Simon Krajewski
Simon Krajewski
Could you describe the actual problem? I can't really make it out from looking at that test.
I can't immediately tell what the difference is between referencing `Baz` on the command line vs. referencing it from `Main` itself, e.g. via a `typedef X = Baz` at the...
Flushing what exactly, and where does that normally occur?
It's unlikely to be a good fix because it doesn't address the `typedef X = Baz` case. We can merge it to get the test, but let's keep an issue...
This seems consistent, I don't think we should allow augmenting existing modules with more fields like this. You can use `Context.defineModule` in such cases.
I can see where you're coming from because this is right in the frontier between fields and types, but ultimately we're still adding fields to a type (even if it's...
Indeed. I wonder if we could give a better error for such cases.
I... don't think this can be fixed in the old protocol.
Yes but the position is also separated with a `@`. It's `file@pos@mode`, _and_ the mode is optional. So with `fi@le@pos@mode` we are in a bad spot.
Not sure what you mean, something like `/something/@Projects/File.hx@12@position` is just the case I mention. Or do you think we should try to find the `File.hx` first and then take it...