Hi Jesse,
I would wish a specific feature that is not listed in the "issues".
Its about a simplified binding of constants and somehow analog to the
@Provides feature.
The common way to bind a constant:
class MyModule extends AbstractModule {
public void configure(){
bindConstant().annotatedWith(SomeBindingAnnotation.class).to
("Hello, World!");
}
}
The additional way i propose:
class MyModule extends AbstractModule {
@SomeBindingAnnotation
String myConstant = "Hello, World!";
...
}
The other issue is regarding the Named annotation. Actually, I never
use it, because its too dangerous that name conflicts might occur.
Instead, I have a custom implementation that also allows to define an
additional Class field (I set this to the class where the constant is
injected) to avoid possible conflicts. I'm really not sure how many
people use the Named annotation in bigger projects, so it might be
considered to add the additional Class field.
Regards,
Martin
On Aug 1, 2:52 pm, "[email protected]" <[email protected]> wrote:
> On Jul 31, 5:03 pm, Karthik Krishnan <[email protected]> wrote:
>
> > Perhaps we could have users vote on this using AppEngine moderator. Kevin
> > Bourrillion (I hope I am spelling his last name correctly) used it to
> > solicit feedback for Google Collections project. Perhaps Guice can leverage
> > the same.
>
> If there's a specific bug or feature you're passionate about, you can
> vote by starring the issue in our tracker.
> http://tinyurl.com/guice-issues
>
> FYI, we're quite cautious about certain changes, particularly those
> that makes it more difficult to reason about an application.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"google-guice" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/google-guice?hl=en
-~----------~----~----~----~------~----~------~--~---
