Re: Save `nil' from the mutant void, preserve the truth of falsehood, prevent the falsehood of truth

[Stefan Monnier]

> `#1=', and related reader syntax constructs aren't bad.

In source code, they are.  In source code, you have other ways to
express sharing, such as `let', which are much preferred.

> Indeed, they are quite prevalent in byte-code files and the language
> would be hamstrung without them.

Which language?  Note that AFAIC .el and .elc files use
2 different languages.

>> - unintern takes a symbol as argument, not a boolean, so it should
>> not be called with the return value of (fboundp ...)
> No, the argument to `unintern' can be a symbol or string.

Who cares, it's still not a boolean.

>> - calling unintern without an obarray arg is a bad idea.
> Yeah,

So: why do you do it?

>> Maybe we should make the second argument mandatory.
> That would be nice.

Indeed.

>> since `intern' only takes a string rather than a symbol.
> Yeah, but again there is the weird corner case of interning the 0
> length string.

What's weird about it?


        Stefan