Skip to content
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

Fix return_const for static methods #47

Merged
merged 2 commits into from
Sep 3, 2019
Merged

Fix return_const for static methods #47

merged 2 commits into from
Sep 3, 2019

Conversation

asomers
Copy link
Owner

@asomers asomers commented Sep 3, 2019

Fix return_const for static methods

1) After locking the Mutexes, I wasn't checking them for PoisonErrors
2) Tests that should_panic need to operate on separate methods so they
   don't poison other tests.
3) The automock_module and automock_foreign_c tests were missing mutex
   protection
This always should've been there, but was left out due to oversight.
The consequence was that return_const couldn't be used with a static
method unless it was preceded with a with or withf.
@asomers asomers merged commit 0deadb0 into master Sep 3, 2019
@asomers asomers deleted the static_return_const branch September 3, 2019 00:18
asomers added a commit that referenced this pull request Jun 6, 2020
This was left out of PR #47 as an oversight.  That PR only fixed
return_const for non-generic static methods.
asomers added a commit that referenced this pull request Jun 6, 2020
This was left out of PR #47 as an oversight.  That PR only fixed
return_const for non-generic static methods.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant