Possibly find a way to separate out the advanced Binder methods about guice

[gissuebot]

From chris.nokleberg on February 28, 2007 13:03:22

If it's really just a documentation issue you could add an AdvancedBinder interface
and make Binder extend AdvancedBinder. This might fall under the "nothing good"
category though.

[gissuebot]

From kevinb9n on February 28, 2007 13:18:14

interesting javadoc hack, but yeah :-)

[gissuebot]

From crazyboblee on February 28, 2007 13:23:26

Ha ha, I was just thinking the exact same thing, Chris. The user would click through
to Binder from Module and only see the relevant methods. This is similar to how
ContainerBuilder->SourceConsumer used to work.

[gissuebot]

From crazyboblee on February 28, 2007 14:03:01

We could also put AdvancedBinder in the spi package.

[gissuebot]

From chris.nokleberg on February 28, 2007 14:30:17

You could also leave out the interface inheritance but still have an AdvancedBinder
and just force people to cast the Binder if they need to access those methods.

[gissuebot]

From crazyboblee on February 28, 2007 14:36:17

Nah, casting sucks. Kevin suggested having a Binder.advanced() method at one point.

[gissuebot]

From crazyboblee on February 28, 2007 14:37:12

I don't think this is a big issue. Given the nature of the DSL, it will be easier to
learn this stuff from a users' guide than directly from the API anyway.

[gissuebot]

From kevinb9n on March 12, 2007 18:14:43

I'm going to close this one.  It's not a big problem and would be hard to do anything
about now that we've released.

Status: WontFix