Reference:
scala/scala#7540

* Remove Unicode arrows (deprecated in Scala 2.13)

Reference:
scala/scala#7540

* Linter: Fix unused config parameter

SuperSafe: Remove usage of .equals
Scalafix: remove unused imports & private hex function

There is no need to guard against LHS null in Scala equality and isInstanceOf

* Remove some hidden typos

* Bump legacy Scala to 2.12.8

* Enable TLS security in README, bump shields to Scala 2.13

- final case classes
- no return() statements
- use ASCII arrows instead of unicode arrows `⇒`, `←` and `→`
- avoid '+' for string concatenation

ref:
Scala best practices https://nrinaudo.github.io/talk-scala-best-practices/#72
Issue #14 #14
ASCII arrows scala/scala#7540

As of Scala 2.13, Unicode arrows are deprecated:

* scala/scala#7540
* scala/scala-dev#585
* scala/bug#11210

Using one will give a deprecation warnings like so:

> The unicode arrow `⇒` is deprecated, use `=>` instead. If you still wish to
> display it as one character, consider using a font with programming ligatures
> such as Fira Code.

As such the Scala layer's version slick capability to replace ASCII arrows with
Unicode ones is no longer useful, and I have removed it.

Based on my tests it doesn't seem that there is a need for a more graceful way
to deprecate this: i.e. nothing fails if there is extra junk in `:variables`.

As of Scala 2.13, Unicode arrows are deprecated:

* scala/scala#7540
* scala/scala-dev#585
* scala/bug#11210

Using one will give a deprecation warnings like so:

> The unicode arrow `⇒` is deprecated, use `=>` instead. If you still wish to
> display it as one character, consider using a font with programming ligatures
> such as Fira Code.

As such the Scala layer's version slick capability to replace ASCII arrows with
Unicode ones is no longer useful, and I have removed it.

Based on my tests it doesn't seem that there is a need for a more graceful way
to deprecate this: i.e. nothing fails if there is extra junk in `:variables`.

As of Scala 2.13, Unicode arrows are deprecated:

* scala/scala#7540
* scala/scala-dev#585
* scala/bug#11210

Using one will give a deprecation warnings like so:

> The unicode arrow `⇒` is deprecated, use `=>` instead. If you still wish to
> display it as one character, consider using a font with programming ligatures
> such as Fira Code.

As such the Scala layer's version slick capability to replace ASCII arrows with
Unicode ones is no longer useful, and I have removed it.

Based on my tests it doesn't seem that there is a need for a more graceful way
to deprecate this: i.e. nothing fails if there is extra junk in `:variables`.

As of Scala 2.13, Unicode arrows are deprecated:

* scala/scala#7540
* scala/scala-dev#585
* scala/bug#11210

Using one will give a deprecation warnings like so:

> The unicode arrow `⇒` is deprecated, use `=>` instead. If you still wish to
> display it as one character, consider using a font with programming ligatures
> such as Fira Code.

As such the Scala layer's version slick capability to replace ASCII arrows with
Unicode ones is no longer useful, and I have removed it.

Based on my tests it doesn't seem that there is a need for a more graceful way
to deprecate this: i.e. nothing fails if there is extra junk in `:variables`.

Unicode arrows are deprecated in Scala 2.13, thanks to
scala/scala#7540 merged in January 2019. For
consistency, unless there's been a conscious decision to _un_deprecate
them, we should continue that on into Scala 3.

Unicode arrows are deprecated in Scala 2.13, thanks to
scala/scala#7540 merged in January 2019. For
consistency, unless there's been a conscious decision to _un_deprecate
them, we should continue that on into Scala 3.