VitWW

About concerns of "Alternating become and return calls" and "Operators are not supported". I propose, that `become` keyword works without warnings only with functions, which are marked with `#[recursive]`/`#[must_become]` or...

> Maybe it would add some layer of transparency at the huge cost of having to attribute all functions while tail calls are a property of the call and not...

### First, > **Dedented string literals must begin with a newline** > 1. The opening line (the line containing the opening quote ") > Must only contain a literal newline...

@programmerjake > > change the rule to _Dedented string literals must begin with a newline_ **or whitespaces and a newline** > > I think that's a good idea. Thank you!...

> @nik-rev Another downside here is that if we ever want to add something like info strings in the future, it'll be much harder I really don't see how **whitespaces**...

@ssendev I also prefer explicit indentation, but I prefer the last line with closed quote to to indicate the indentation ```rust let sql = d" create table student( id int...

As an alternative: Rust use `*mut` and `*const` for raw pointers. So it is handy to reuse this keyword here ```rust let (x, const y, mut z) = &mut xyz;...

For context, an alternative to ref/move > (`ref` | `move`)? `mut`? IDENTIFIER (@ PatternNoTopAlt)? is mut/const > `ref`? (`const`| `mut`)? IDENTIFIER (@ PatternNoTopAlt)? or both

@steffahn That's why `const` (not `mut`) is an alternative to `move`/ `value`(not `ref`). It is already in use for raw types, and the content of immutability is clear

For example, quite recently PHP added to v7.3 indentation to [PHP Heredoc](https://www.php.net/manual/en/language.types.string.php#language.types.string.syntax.heredoc) Strings. So, it is useful feature