-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
Implement log in rust #554
Comments
pcwalton wound up implementing a general purpose log using shapes in C++ instead. Or do you mean a different part of it? |
Well, we could still move the code that checks the flag and figures out whether to log in rust. |
pcwalton says it would be easy at this point to turn the log statements into library functions |
but to preserve line numbers we would have to make it a syntax extension |
I think #3627 subsumes this. Reopen if you disagree. |
Updates the requirements on [quickcheck](https://github.com/BurntSushi/quickcheck) to permit the latest version. - [Release notes](https://github.com/BurntSushi/quickcheck/releases) - [Commits](https://github.com/BurntSushi/quickcheck/commits/0.7.1) Signed-off-by: dependabot[bot] <[email protected]>
Document wasm_import_module for #[link].
…g#554) * Introduce documentation for building a larger cargo project * copyright on script * Edits in response to feedback
Remove dummy value locals for function ptr calls
With global variables implemented, we can probably implement log in rust itself.
The text was updated successfully, but these errors were encountered: