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

Implement derived type descriptors in rustc #213

Closed
graydon opened this issue Jan 27, 2011 · 1 comment
Closed

Implement derived type descriptors in rustc #213

graydon opened this issue Jan 27, 2011 · 1 comment

Comments

@graydon
Copy link
Contributor

graydon commented Jan 27, 2011

Rustc doesn't know how to do derived type descriptors. This is necessary for generic objects and closures (the tydesc for the captured body has a derived type).

@graydon
Copy link
Contributor Author

graydon commented Feb 18, 2011

Fixed in 2b66900.

dlrobertson pushed a commit to dlrobertson/rust that referenced this issue Nov 29, 2018
Aaron1011 pushed a commit to Aaron1011/rust that referenced this issue Oct 26, 2020
ZuseZ4 pushed a commit to EnzymeAD/rust that referenced this issue Mar 7, 2023
matthiaskrgr pushed a commit to matthiaskrgr/rust that referenced this issue Mar 7, 2023
carolynzech added a commit to carolynzech/rust that referenced this issue Feb 19, 2025
Adds a GitHub Actions workflow that downloads VeriFast and runs
`verifast-proofs/check-verifast-proofs.mysh`. (`mysh` is a simple tool
that ships with VeriFast for running simple scripts. It is optimized for
running test suites (and used to run [VeriFast's test
suite](https://github.com/verifast/verifast/blob/master/testsuite.mysh).
Works on Linux, Mac, and Windows.)

See rust-lang#238 to see how this can be used to verify the `linked_list.rs`
(Challenge 5) solution.

Resolves rust-lang#213

By submitting this pull request, I confirm that my contribution is made
under the terms of the Apache 2.0 and MIT licenses.

---------

Co-authored-by: Carolyn Zech <cmzech@amazon.com>
Co-authored-by: Rémi Delmas <remi.delmas.3000@gmail.com>
This issue was closed.
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

No branches or pull requests

1 participant