scala.quoted.Quotes.reflectModule.SymbolModule is incomplete

[rcano]

Compiler version

latest nightly and prior.

Problem

In order to create new symbols, we must use Symbol api, when augmenting a class in an annotation macro, there's no way to add new members to its symbol because there's no right way to copy the original attributes, for instance flags are missing, there's no direct primary constructor (maybe this is supposed to be a decl method with flags). Ironically, the newModule method does allow you to pass the flags for the class.

[bishabosha]

perhaps you could give a specific example of something you want to achieve?

[rcano]

perhaps you could give a specific example of something you want to achieve?

I did in the first post. I want to augment an annotated class with an annotation macro. I want to add new methods to it that are visible (not just bytecode generated, because you can do this by modifying its tree)

[bishabosha]

but its specifically intended that you can't add new visible members with an annotation macro

perhaps you could give a specific example of something you want to achieve?

The point of this question is that maybe you can get the same effect with a different technique, but I don't know the use case.

[nicolasstucki]

I want to add new methods to it that are visible (not just bytecode generated, because you can do this by modifying its tree)

This is disallowed by principle in macro annotations. We decided to restrict this because causes fundamental problems with the Scala type system and compilation scheme.

[rcano]

So is that the argument for Symbol.newClass being impaired compared to Symbol.newModule ? I'll have to test newModule to see if it really can't expose new symbols.
Also I'm using this annotation macro as an alternative to code generation, because there are no tools at all to reflect over scala code and generate code in an non stringly manner

This is disallowed by principle in macro annotations. We decided to restrict this because causes fundamental problems with the Scala type system and compilation scheme.

So I should use the annotation macro to produce the bytecode that has my new definitions, ship this in a library and use it as a dependency? because this does seem to work, it just is an obnoxious intermediate step, like the old scala 2 macros and their separate staged compilation.