We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
With nim version 2.0
After fixing: (datetime2human MR) + (nim_websitecreator MR)
./nimwc gives the following error
std/asyncmacro(250, 31) Error: 'matchMatcher (Async)' is not GC-safe as it accesses 'storageEFS' which is a global using GC'ed memory
To fix this variable has to be declared as threadvar and initialized later (without using let)
var storageEFS* {.threadvar.}: string storageEFS = block: ... path
./nimwc will now result in error
std/asyncmacro(250, 31) Error: 'matchMatcher (Async)' is not GC-safe as it calls 'sendEmailActivationManual'
To fix this proc has to marked as .gcsafe along with .async
proc sendEmailActivationManual*(email, userName, password, activateUrl, invitorName: string) {.async, gcsafe.} =
std/asyncmacro(250, 31) Error: 'sendEmailActivationManual (Async)' is not GC-safe as it calls 'genEmailMessage'
proc genEmailMessage*(msgContent: string): string {.inline, .gcsafe.} =
If proc marked as gcsafe depends on global variable then they should be declared as {.threadvar.} and initialized safely.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
With nim version 2.0
After fixing: (datetime2human MR) + (nim_websitecreator MR)
./nimwc gives the following error
To fix this variable has to be declared as threadvar and initialized later (without using let)
./nimwc will now result in error
To fix this proc has to marked as .gcsafe along with .async
./nimwc will now result in error
If proc marked as gcsafe depends on global variable then they should be declared as {.threadvar.} and initialized safely.
The text was updated successfully, but these errors were encountered: