5 ms·

`import Y from X` is a terrible language design decision, established by the JavaScript ecosystem. It should be along the lines of `import X.Y` or `from X impor

by Taig 3y ago

`import Y from X` is a terrible language design decision, established by the JavaScript ecosystem. It should be along the lines of `import X.Y` or `from X import Y` so that autocomplete tools can assist you.

napowderly 3y ago
Agreed, we need to flip this.
amonith 3y ago
Disagree. I rarely remember what lib has the class/function/whatever I need. Doesn't help that some libs often use "proprietary" names (e.g. "Uno", "Avalonia", "Rotativa"). I often don't even write "imports" myself. I use stuff in code and let my IDE autoimport stuff.
Timot05 3y ago
Aspects of the python lexer and parser implementation were borrowed from python, which is partly why we ended up here. I do agree though.
- echoangle 3y ago
  Python does from x import y though.
  - Timot05 3y ago
    Yeah, I think we only allow import x from y for the minute. And because we don't have a language server yet, it wasn't obvious that it was an issue. That'll change soon when the server is up though!
mplewis 3y ago
Really? When I type import { someVal in JS, VSCode autocompletes it to import { someValue } from “somePackage”. I haven’t had issues here.