[ENH] provide command line option for enabling legacy noexcept propagation
See original GitHub issueIs your feature request related to a problem? Please describe.
As mentioned in https://github.com/cython/cython/pull/4670#issuecomment-1279918128 introducing default exception propagation in #4670 can introduce compatibility issues for cython users.
Describe the solution you’d like.
New command line option should be provided enabling legacy noexcept propagation as default:
cython -X noexcept ...
Describe alternatives you’ve considered.
No response
Additional context
No response
Issue Analytics
- State:
- Created a year ago
- Reactions:1
- Comments:7 (6 by maintainers)
Top Results From Across the Web
[ENH] provide command line option for enabling legacy ...
Describe the solution you'd like. New command line option should be provided enabling legacy noexcept propagation as default: cython -X noexcept ...
Read more >CHANGES - platform/external/swig - Git at Google
[Java] Patch #15 - Allow the use of the nspace feature without the -package commandline option. This works as long and the new...
Read more >Using the GNU Compiler Collection
Most of the command-line options that you can use with GCC are useful for C programs; when an option is only useful with...
Read more >pybind11 Documentation - Read the Docs
#3254 #3194. • The clang-tidy google-explicit-constructor option was enabled. ... compile and run the target, all from the command line.
Read more >changes - SWIG.org
configure now enables C++11 and later C++ standards testing by default (when ... 2022-03-25: wsfulton The debug command line options that display parse...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
The main advantage of the per-file basis is that I think anything else would be hard to do with the current implementation.
I don’t think it’s terrible for users. I’m sure a lot will just turn it on for their existing code and forget about it. But it does at least provide a solution to not break everything immediately
Hmm as long as I understand this option can be enabled on per-file bases. So users can put it to all files and gradually remove it. But I am not sure if this is good approach for users or not…