Re: [Yaml-core] Seq-in-seq and boolean implicits

[Brian I. <in...@tt...>]

On 20/01/03 09:16 -0700, why the lucky stiff wrote:
> Oren Ben-Kiki (or...@be...) wrote:
> > 
> > We could allow '-' as a plain value only when it is not ambiguous. The
> > full list of cases where it is not ambiguous is:
> > 
> >     As *in-line* value: -
> >     As next line *typed* value:
> >         ! -
> >     ! - : As a *typed* key
> >     In flow map: { - : false, false: - }
> >     In flow seq: [ -, + ]
> > 
> > It would only be ambiguous when used as non-typed key or non-typed
> > next-line plain scalar:
> > 
> >     - : Ambiguous # Null map-in-seq key)
> >       Ambiguous:
> >         - # Null seq entry?
> > 
> 
> *shiver*
> 
> I'm sorry, but this is just too much work to implement with too little
> gain.  In addition, we'd have to instruct users about this sort of
> exception to the rule.
> 
> Let's just stick to what we have and perhaps a better alternative will
> surface.

Hate to say it, but "YAGNI". 

Actually I love to say it. :)

Boolean implicits are so yagni. You can use any string you want. 

    verbose_log: no
    #email_on_error: 0
    email_on_error: in...@tt...

Just let the application make sense of it. It's a *config file* for
goodness sake. I've never used boolean objects for configuration
switches. yagni.

Booleans for serialization may be needed, but in that use case

    ---
    - !bool 1
    - !bool false

is fine.


Cheers, Brian