Christoffer Lerno
Christoffer Lerno
Exactly, it will be limited to single level for readability and also implementation should be more straightforward.
Just as a clarification: This thing is valid today: ```c fn void std::core::String.new_thing(self) {} ``` And is nothing special, just an unambiguous way to write: ```c fn void String.new_thing(self) {}...
Having investigated the complexity and the look of it, it looks like it's not worth it.
Possibly yes, there are ways to do this such as: ```java /** * This will get you the [Foo] value stored in [my_module::global_foo]. **/ ```
Some concerns: 1. The doc might refer to variables that are private or not imported. 2. If the docs are in a .c3i, the identifiers might refer to identifiers that...
But let's say we do this to some extent. At least we should try to do this for docs to be able to link things up. What format should we...
That is probably true yes.
An alternative is to make it configurable as a build parameter: `--echo-prefix myecho`