Exploring the future of symbolic expressions, functional language // colon description

Permanent night (871863191) 18:13:05
I think the future programming language should be more integrated with mathematics.
Introduce more mathematical ideas and models into programming language design
In fact, many things of C ++ have better reflected this point.
Anonymous support (519398990) 18:17:13
No, the goal of modular function evolution is not to let mathematics and integration show, but to block these computing details
Instead
Anonymous support (519398990) 18:18:59
In the future, language evolution should be a simplified syntax form that provides a simpler way of reading and writing code.
Anonymous support (519398990) 18:20:20
I mean, the future is a more ideal expression of those important symbols.
Permanent night (871863191) 18:24:39
You are engaged in Engineering.
Anonymous support (519398990) 18:30:33

{} // Modular () // Function Definition and call, expression priority [] // container and subscript index, () {} combined with // function definition, process control syntax // to be extended; iterative function calls make function calls and Lambda perfectly express; in fact, the process control syntax also makes sense. It is similar to the syntax [] {} // to be extended like a function: used to define a new type of data structure. In this way, the struct/class keywords are not required.

Anonymous support (519398990) 18:33:55
If this type of programming grammar appears, Microsoft will be convinced, and he should be doing better in terms of syntax extension.
Anonymous support (519398990) 18:40:11

= // Value assignment, to be constrained. When it appears in an expression, it becomes a logical comparison semantics. This eliminates the hard and bitter expressions such as the following: // number, to be blocked, the colon is transformed into a target declaration, so that no auto keyword is needed. The label and the goto sentence are eliminated. The switch control sentence is to be designed separately.

Anonymous support (519398990) 18:48:19
In fact, the direct transformation

switch (exp){case(exp1){// process block}case(exp2){// process block}case()//Like the default{}}

Everything works in a functional expression.

try{...}catch(){...}

Isn't catch like this?