Closed parir closed 7 years ago
That's an atom-build-cargo issue. https://github.com/AtomBuild/atom-build-cargo
I thought we fixed this :/
Do you have an example code triggering this?
Also we need the rustc version
Even a fresh cargo new --bin hello
will trigger the error. :/ Maybe related to the new atom-build-cargo version?
rustc 1.13.0 (2c6933acc 2016-11-07) cargo 0.13.0-nightly (eca9e15 2016-11-01)
I really wonder about javascript's sanity sometimes. Why in the world is var f = function(foo) { g(foo, 5) };
not an error?
Sorry about that. I yanked 1.1 and I'll publish a new one asap. you can probably downgrade to 1.0 with apm install build-cargo@1.0
and 1.1.1 has been published with a fix.
Works like a charm!
Off-topic:
var f = function(foo) { g(foo, 5) };
is valid javascript, because it means:
foo
as argumentg(foo, 5)
Keep in mind that functions are, like everything, objects in javascript.
The only thing that a good linter could complain about, is that you miss a semi-colon after the )
from g(...)
(but that's optional, and only stylish)
I know... I've just gotten too comfy in typesafety to remember such things
[Enter steps to reproduce below:]
Atom Version: 1.12.6 Electron Version: 1.3.9 System: "Fedora release Thrown From: build package, v0.67.0
Stack Trace
Uncaught TypeError: Cannot read property 'map' of undefined
Commands
Config
Installed Packages