Re: [elpa] externals/transient 667ce2b287 18/23: Use transient-default-value in transient-init-value(suffix)

[Stefan Monnier <monnier@iro.umontreal.ca>]

> The reason I am using Eieio's "this is not bound", is that I am doing an
> Eieio thing here.  It's not a "not bound" slot but the "not bound"
> return value of a generic function, which isn't the same thing, but
> pretty damn close.

🙂

> Sure I can invent a new symbol just for this one case, but it would be
> (IMO unnecessary) noise and the only reasons I would be doing it is to
> make you happy and to avoid having a conversation about it.

Sorry about this conversation.  I'm not bothered by your use of
`eieio--unbound`, to be honest, I was just curious.

[ If I were you, I think I'd just use something like `:unbound` or
  `:transient--unbound` because it's literally less code than what you
  currently have and it would save me from having to worry about the
  annoying guy breaking compatibility again.  ]

>> IOW, is there a good reason to break the abstraction here?
> I am not sure what "the abstraction" and "here" refer to exactly.

One of the abstractions is just that the `eieio--` prefix implies it's an
internal entity to EIEIO so shouldn't be used from outside of EIEIO's
own code.

The other is that `eieio--unbound` is a value that ideally noone should
ever see, just like `Qunbound` in Emacs's C code.  Every time you use it
you increase the risk that someone ends up storing it inside an
EIEIO object.
[ Now that I think about it... I'm no fan of EIEIO objects, especially
  that notion of a slot being unbound, so maybe I should encourage use
  of `eieio--unbound` so as to maximize the chance of mayhem.  🙂  ]


        Stefan