Its implemented as an accessmodifier ( named 'final') rather than a keyword
Java doesnt have (c# equiv) const - its final variables act like c# readonly, (static) final variables may be computed statically at compile time if possible
The promise cobra makes as to the meaning of const vs readonly/final ( if directly supporting both) is going to be a bit weaselly depending on the back end support for
the same concepts.
Hence I'd suggest promising direct support for runtime initted constants with the (weaker) promise of best effort for compile time support if supported by backend
(const keyword, combinatorial for weaker promise) worst case is that you only get readonly equivalent which is probably most desirable situation anyway.
I dont see val/value as being significantly better than const for indicating some form of variable immutability, much the reverse in fact ( same as var)
perhaps we could go for a more truthful keyword 'as_const_as_we_can_get' ( acawcg) for indicating the constantness cobra is providing
