Bootstrapped compiler wish list

[Adrian Pop]

Here is a list of what me and Per talked about:

1. Include the uniontype path to the uniontype record, i.e. Abyn.Path.IDENT
2. Make it possible to use Absyn.Path.IDENT.name instead of matching for it. Make also possible to use Absyn.Path.IDENT.name = x; This will make writing of set/get functions much easier.
3. Support anonymous records from uniontypes in crefs or paths, i.e. DAE.Equation._.info = newInfo; This will bind the component named info form any record inside DAE.Equation to newInfo;
4. Support opaque types and type methods. I.e.

   package P
     type X
       protected type Name;
       function fGet(Name) => something;
       function fSet(Name) => something;
     end X;
   end P;
   

Add more here if you want to.

[Per Östlund]

A comment about point 4. I would like to be able to instantiate X, and then use X to access to functions associated with X. E.g.:

ComponentRef cref;
_ := ComponentRef.lastIdent(cref);

[Martin Sjölund]

This ticket was not closed for 1.9.1, which has now been released. It was batch modified for milestone 1.9.2 (but maybe an empty milestone was more appropriate; feel free to change it).

[Martin Sjölund]

Milestone changed to 1.9.3 since 1.9.2 was released.

[Martin Sjölund]

Moved to new milestone 1.9.4

[Martin Sjölund]

Milestone pushed to 1.9.5

[Martin Sjölund]

Milestone renamed

[Martin Sjölund]

Ticket retargeted after milestone closed

[Martin Sjölund]

Milestone moved to 1.12.0 due to 1.11.0 already being released.

[Francesco Casella]

The milestone of this ticket has been reassigned to "Future".

If you think the issue is still valid and relevant for you, please select milestone 1.13.0 for back-end, code generation and run-time issues, or 2.0.0 for front-end issues.

If you are aware that the problem is no longer present, please select the milestone corresponding to the version of OMC you used to check that, and set the status to "worksforme".

In both cases, a short informative comment would be welcome.