Compiler plugin or Meta Plugin annotation ?

[Maxime Lévesque]

 I've been thinking about scalac compiler plugins lately,

what would the scalite audience think about scalac
understanding a @CompilerPlugin annotation, that
would load a (compiler) plugin without the need
for extra command line configuration ?

 Would it be possible to implement this feature
as a phase0 (meta) plugin ?

 One plugin to load them all ?

 Of course this could have the consequence of a
proliferation of plugins, everyone and his mother in law
would write plugins, leading to a dark era of plugin hell
that would make the dll, jar hell pale in comparison !;)

 Cheers

[Brian Maso]

I think it sounds like a great idea. I could include my project's necessary plugins in the same codebase as the code itself.

I use Maven for my projects usually, so I can also imagine using Maven scalac configuration to explicitly list my project's compiler plugins. I don't have enopugh imagination to know which of these two options would be "best" for me during development.

Best regards,
Brian Maso
[phone]
brian@...
twitter: @bmaso
skype: brian.maso
LinkedIn: http://www.linkedin.com/in/brianmaso

2009/10/30 Maxime Lévesque <maxime.levesque@...>

 I've been thinking about scalac compiler plugins lately,

what would the scalite audience think about scalac
understanding a @CompilerPlugin annotation, that
would load a (compiler) plugin without the need
for extra command line configuration ?

 Would it be possible to implement this feature
as a phase0 (meta) plugin ?

 One plugin to load them all ?

 Of course this could have the consequence of a
proliferation of plugins, everyone and his mother in law
would write plugins, leading to a dark era of plugin hell
that would make the dll, jar hell pale in comparison !;)

 Cheers