Thank you for sending feedback.
I am aware of the nature of FactoryDefaults/ApplicationDefaults. It's a
good system, easy to understand, and works.
I have thought about this before posting as I use something similar already
in my code. I don't have default value conflicts, however, I do
occasionall
I can see one problem here -- nothing prevents you from specifying more
than one @DefaultValue and you may get a conflict too late, as far as I see
you can't control this. Have you thought about it?
On Tue, May 28, 2013 at 12:23 AM, Eli Doran wrote:
> I've used @Symbols a lot. I appreciate its
Having an optional default value on @Symbol seems useful to me.
On Mon, May 27, 2013 at 4:42 PM, Thiago H de Paula Figueiredo <
thiag...@gmail.com> wrote:
> On Mon, 27 May 2013 17:23:36 -0300, Eli Doran wrote:
>
> I've used @Symbols a lot. I appreciate its flexibility and coercion
>> ability.
>
On Mon, 27 May 2013 17:23:36 -0300, Eli Doran wrote:
I've used @Symbols a lot. I appreciate its flexibility and coercion
ability.
I started programming around it though and instead accessing SymbolSource
and TypeCoercer directly because it is missing the ability to specify a
default value, a
I've used @Symbols a lot. I appreciate its flexibility and coercion ability.
I started programming around it though and instead accessing SymbolSource
and TypeCoercer directly because it is missing the ability to specify a
default value, and the ability to ignore when a value can't be found.
I ma
