--strict should disallow implicit string concatenation
#837
Labels
Milestone
Comments
evhub
changed the title
--strict should warn about implicit string concatenation--strict should disallow implicit string concatenation
Merged
evhub
added a commit
that referenced
this issue
Jun 9, 2024
See Coconut's [documentation](http://coconut.readthedocs.io/en/develop/DOCS.html) for more information on all of the features listed below. Language features: * #833: New `case def` syntax for more easily defining pattern-matching functions with many patterns. * #811: New `f(name=)` syntax as a shorthand for `f(name=name)`, replacing the now deprecated `f(...=name)` syntax. * #836: New `CoconutWarning` built-in used for Coconut runtime warnings. Compiler features: * #837: Coconut will now warn about implicit string concatenation and disable it completely with `--strict`. * #718: Coconut will now warn about use of `addpattern def` without a prior `match def`. This was a previously-supported feature to make pattern-matching functions with many patterns easier to write, but the new recommended way to do that is now via `case def`. * #785: Initial [pyright](https://github.com/microsoft/pyright) support via the `--pyright` flag. Bugfixes: * #839, #840: Fixed some f-string parsing issues. * #834: Fixed `len` of empty `zip` objects. * #830: Improved use of colored output. * #757: Improved PEP 695 support on Python 3.12.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It's a pretty classically bug-prone Python feature (e.g. it can hide missed commas), so it might be worth warning about it in
--strictmode. We can even consider compiling string literals added together with plus into implicit string concatenation to avoid the performance hit.The text was updated successfully, but these errors were encountered: