chriseth

It is not really a duplicate, but there are examples of what is planned. Something like `alias x = complicatedtype` or `using x = complicatedtype` or `type x = complicatedtype`.

I think we should not silently normalize the paths. Instead we should not allow `.` or `..` as part of a filename in standard-json. In standard-json, the file paths are...

This sounds a lot like the `--base-path` option we already have.

The `Expected identifier` errors are from the parser - I guess it has a missing "use keyword for identifier" workaround, which maybe is also just fine.

If we allow `h.selector`, we have to check whether the function's parameters are valid outside of the contract which turns this into an even more complicated rule.

I think these are two unrelated issues: - `this.g.address;` should parse. In general, `.address` should be valid everywhere in the parser. - `g.selector;` should not work.

Acutally there are quite complicated rules about `.selector` and maybe it's best to just leave them as they are...

Can someone check how coloured strings would be displayed by e.g. remix or vs code?

I think I like the `{signature = "..."}` syntax most, but I would prefer to not have the option to allow to change the selector. Also, do we want to...

Comments from call: We should use `:` instead of `=` and we should also allow this for function types.