Remove `be`

[brson]

It's currently just a rarely tested synonym for ret. Regardless of whether we eventually decide to implement tail calls, be is not doing anything for us today.

Don't forget to remove it from the manual too.

[graydon]

Not presently, but it's necessary to differentiate tail-call from non. So this is blocked on whether-we-keep-tailcalls.

[brson]

I'm suggesting we unblock it and just remove the keyword since the tail call decision seems like it's going to be pushed back forever. We could leave be a reserved word as insurance. Either way it's not a big deal since there's so little code dedicated to be.

[catamorphism]

I agree with @brson . Bit-rotted code is not good. We can always reintroduce it later.

[graydon]

ok