You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Use String.contains?/2 when the right side is a string or
String.match?/2 when the right side is a regex.
The goal of this deprecation is to make space for the upcoming
`~` and `~=` operators.
Copy file name to clipboardExpand all lines: CHANGELOG.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,6 +16,7 @@
16
16
* Deprecations
17
17
*[Kernel]`binary_to_term/1`, `binary_to_term/2`, `term_to_binary/1` and `term_to_binary/2` are deprecated in favor of their counterparts in the `:erlang` module
18
18
*[Kernel]`//` for default arguments is deprecated in favor of `\\`. This is a soft deprecation, no warnings will be emitted for it in this release
19
+
*[Kernel] Deprecate `=~` in favor of `String.contains?/2` (for strings) and `String.match?/2` (for regexes)
19
20
*[Kernel] Deprecate `@behavior` in favor of `@behaviour`
20
21
*[Record] Deprecate `to_keywords`, `getter` and `list getter` functionalities in `defrecordp`
IO.write:stderr,"left =~ right is deprecated, please use String.match?/2 (for regexes) or String.contains?/2 (for strings) instead\n#{Exception.format_stacktrace}"
IO.write:stderr,"left =~ right is deprecated, please use String.match?/2 (for regexes) or String.contains?/2 (for strings) instead\n#{Exception.format_stacktrace}"
0 commit comments