Rfcs: Call for deprecating stupy design and old fasion

[lyrachord]

At first, there is no need to argue the philosophy behind of the subject.
Indeed, it's obvious that there always has stupy, what's more, even a clever man will make mistakes as well.

Any one can make proposal here, recommended format: target, reason, example,todo

At a proper moment, someone assembles it to make a formal RFC.

[lyrachord]

target: remove shadow, the reuse of immutable variable.
reason: confuse user, and give change to let user be wrong
example: tooooo maaaany, ignore

[lyrachord]

target: refining the word variable.

reason: rust distinguish immutable already, and variable is vary-able, immutable is not vary-able, so need to correct all occurs of variable in rust.

example: no need

todo: name is the hardest thing. Most war just because of name and naming.
candidates can be: refer, representation
Don't be entangled between noun. and verb. Because English is ugly, just to treat it as a meaningful symbol is OK. And Computer does not need a natural language even now.

[lyrachord]

target: unify dot operation, remove ::
reason: hard to read and write for programmers. Semantics processing should be able to distinguish the statical and dynamical cases. So the responsibility belongs to the compiler instead of users.

[lyrachord]

target: simplify data type suffix.
Use bytes 1/2/4/8/ instead of bits 8/16/32/64

reason:
typing more easier.
save human memory.
save human math evaluation ability, and too many people has a bad capacity of math.

todo:
proposal types: i1/2/4/8, u1/2/4/8/, f4/8.
And Although SIMD contains inst with f2 operand, they should not be used at most cases.

[Manishearth]

I'm closing this; your comments don't really make much sense, they propose breaking changes to Rust, and are very light on the details.