Daniel X Moore
Daniel X Moore
Maybe : for named export, ^. for property? And plain . is always part of the file name. We’ll need to play around to see what we prefer to be...
I think `//` is pretty interesting for the named export. ``` ^lodash/add ^lodash//add ``` ```js import ref from "lodash/add" import { add as ref1 } from "lodash" ``` The advantage...
If the quoted strings exist as a fallback we could do a more concise prefix caret for common cases: ``` ^underscore/modules/map // import ref from "underscore/modules/map" ^underscore.map // import {...
We could also consider snug ~`:` and~ `::` in this context as a scope resolution kind of thing. Edit: forgot about `:` in paths but `::` is probably ok.
@johndeighan You should be able to use: ``` { "parseOptions": { "deno": true } } ``` In your Civet config.
One thing to note is that this will prevent a possible alternative `break` expression analogous to `throw` in expression position. ``` while true x = if b then break else...
I think we can still use `break` as a special condition inside `if/unless` immediately following an iteration expression. I'm wary of allowing `break` as an expression to have indefinite scope.
Maybe `break?` for the value
`break.value` could be used for the value passed from `break with`.
I think using escape to unfocus the code editor and allow navigating to the next interactive element with tab is a good idea. It would also be nice to indent...