-
Notifications
You must be signed in to change notification settings - Fork 16
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
Invalid memory access caused by Spectator, should it be removed? #29
Comments
@wout thanks for this Issue. Seems like removing Spectator is a correct way to go... |
Great, I'll work on that. |
Thanks a lot! I can help if anything needed. |
Great! I may have some questions here and there, I'll let you know. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm preparing a PR on this shard to fix a few hanging issues, but I'm running into the following error after running
crystal spec
:I've already removed the cache, but that doesn't help. Since the Spectator shard also causes other issues (#14), I wonder if it should be removed for maintainability. Other than the RSpec-like feeling Spectator brings, are there any benefits over Crystal's native testing framework? I wouldn't mind doing it.
The text was updated successfully, but these errors were encountered: