|Subject:||Re: proposal to make null string handling more emacs-y|
|Date:||Thu, 26 Apr 2012 21:17:36 -0700|
> There's a lot of code out there that's forced to do type assertions onI can believe that (it's often handy to use "nil-in-nil-out" when
> string args that could be simplified if these common functions could
> accept nils.
composing functions which may return nil).
But there's also the risk
that you hide real errors, leading to weird behaviors that are more
difficult to track down.
E.g. one package uses some other package's var before it's initialized,
so with the current semantics you might get a clean error, whereas with
your proposed semantics you might get some weird behavior where the user
why doesn't bar find my thingy even though C-h v foo-var tells me it's
set to "/some/path"?
|[Prev in Thread]||Current Thread||[Next in Thread]|