[This has been merged](https://github.com/jashkenas/coffeescript/pull/4352) and released as part of CoffeeScript 1.12.

[This has been merged](https://github.com/jashkenas/coffeescript/pull/4352) andwill bereleased as part of CoffeeScript 1.12.

[This has been merged](https://github.com/jashkenas/coffeescript/pull/4357) and released as part of CoffeeScript 1.12.

[This has been merged](https://github.com/jashkenas/coffeescript/pull/4357) andwill bereleased as part of CoffeeScript 1.12.

These are nice-to-have features that should be implemented as time permits, probably only in the “new” compiler if one gets created. Any change that causes ES2015 output and isn’t opt-in needs to either be enabled by a flag or only in the new, ESNext-outputting compiler.

Output CoffeeScript’s interpolated strings—`"hello, #{name}!"`—as ES2015 template literals:`` `hello, ${name}!```Thisis in progress at[jashkenas/coffeescript#4365](https://github.com/jashkenas/coffeescript/pull/4365)

[Thishas been merged](https://github.com/jashkenas/coffeescript/pull/4365) into the`2` branch.

[This is has been merged](https://github.com/jashkenas/coffeescript/pull/4306) and released as part of CoffeeScript 1.12.

[This is has been merged](https://github.com/jashkenas/coffeescript/pull/4306) andwill bereleased as part of CoffeeScript 1.12.

These are features we’re not sure we will implement, in any version of CoffeeScript:

When a variable isn’t declared using the new operator that produces`const` (see above), CoffeeScript should automatically declare it with`let` whenever possible.

If we support`let` and`const`,[(#35)](https://github.com/coffeescript6/discuss/issues/35), which would be necessary if we want to gain the block-scope aspects of the new`let` and`const` keywords, we would need two new operators:`:=` for`let` and`:==` for`const`. The`:=`-defined variables would get their`let` declarations grouped together at the tops of their blocks.

When a variable isn’t declared using a new operator that produces`const` (see above), CoffeeScript should automatically declare it with`let` whenever possible.

These are other features that have been discussed, but the consensus at the moment is that no action should be taken to implement them.