-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
A lint for large stack allocation #827
Comments
Is this still true? I thought we were already resizing the stack when needed. Am on mobile right now, but will check. |
I just tried it on the latest nightly and got an overflow. |
OK then. Perhaps it makes sense to check stack sizes on a number of systems first so we can report on what systems an allocation would certainly fail? |
I believe the minimum stack size is available via the environmental variable |
I know. However the value of that variable varies from system to system. For some, 'it runs on my machine' may be OK, but many folks I know want their code to run on other systems, too (or at least aren't directly opposed to that)... |
Right-- I was just pointing it out as an easy way to check the maximum size on different systems. |
Stack allocation of large arrays, such as
[0; 8388608]
should be an error-- they will cause stack overflows.The text was updated successfully, but these errors were encountered: