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.

Sign up for GitHub

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

Jump to bottom

Items losing type parameters over course of typechecking pass. #93

Closed
froystig opened this issue Jun 29, 2010 · 1 comment
Closed

Items losing type parameters over course of typechecking pass. #93

froystig opened this issue Jun 29, 2010 · 1 comment
Labels
A-type-system Area: Type system

Comments

@froystig
Copy link
Contributor

Fix the issue revealed in run-pass/generic-fn-twice.rs. Functions in modules (perhaps more generally items in items) appear to lose their recollection of having any type parameters after their first type unification.
@pcwalton
Copy link
Contributor

New typechecker fixes this. Un-XFAILed as of revision 35e73b0.

mbrubeck pushed a commit to mbrubeck/rust that referenced this issue Oct 17, 2011
@froystig
Address _io.new_buf FIXME now that issue rust-lang#93 is closed.
b9075c2
mbrubeck pushed a commit to mbrubeck/rust that referenced this issue Oct 17, 2011
@graydon
Mop up workarounds in stdlib no longer required as issue rust-lang#93 …
935b434 
…is closed.
@evanmcc evanmcc mentioned this issue Apr 3, 2012
Closed
oli-obk pushed a commit to oli-obk/rust that referenced this issue Jul 19, 2017
@solson
Merge pull request rust-lang#93 from oli-obk/always_encode_mir
cbffb3b 
rustup to rustc 1.15.0-dev (ace092f 2016-12-13)
keeperofdakeys pushed a commit to keeperofdakeys/rust that referenced this issue Dec 12, 2017
@alexcrichton
Merge pull request rust-lang#93 from alexcrichton/nix-additions
0ac0bc0 
Add a load of constants/definitions from nix
kazcw pushed a commit to kazcw/rust that referenced this issue Oct 23, 2018
@AdamNiederer @alexcrichton
Improve _mm256_round_* docs (rust-lang#93)
4492b4c 
Fix a grammatical error, use a list instead of using a code block or nothing,
and add the LLVM immediate reference.
eddyb pushed a commit to eddyb/rust that referenced this issue Jun 30, 2020
@ibabushkin
Merge pull request rust-lang#93 from gnzlbg/fix_exit_code
bd29cd6 
Fix exit code of rust-semverver in tests
antoyo added a commit to antoyo/rust that referenced this issue Sep 28, 2021
@antoyo
Cleanup fix for global initialization (rust-lang#93)
ab4ff2d 
* Cleanup fix for global initialization
* Remove linker script hack
* Use v0 symbol mangling
* Fix warnings
djtech-dev pushed a commit to djtech-dev/rust that referenced this issue Dec 9, 2021
@TheDan64
Add parent checking to BB methods. Fixes rust-lang#93
eeab137
djtech-dev pushed a commit to djtech-dev/rust that referenced this issue Dec 9, 2021
@TheDan64
Merge pull request rust-lang#121 from TheDan64/feature/safer-blocks
136dd5e 
Add parent checking to BB methods. Fixes rust-lang#93
ZuseZ4 referenced this issue in EnzymeAD/rust Mar 7, 2023
@wsmoses @vchuravy
C API (#93)
ea6916f 
* Initial Enzyme C API

* Cpp api

* add merge on TypeTree

* change bool to uint8_t

* fixup! change bool to uint8_t

* fixup! fixup! change bool to uint8_t

* fixup! fixup! fixup! change bool to uint8_t

* fixup! fixup! fixup! fixup! change bool to uint8_t

* Validate c header for rust usage

Co-authored-by: Valentin Churavy <v.churavy@gmail.com>
@Amanieu Amanieu mentioned this issue Jun 12, 2023
Open
celinval pushed a commit to celinval/rust-dev that referenced this issue Nov 29, 2024
@Jimmycreative @QinyuanWu
@carolynzech @zhassan-aws
Contracts & Harnesses for non_null::sub and non_null::sub_ptr and…
688b15b 
… `non_null::offset_from` (rust-lang#93)

Towards model-checking#53

Changes
added contract and harness for non_null::sub
added contract and harness for non_null::sub_ptr

Revalidation
To revalidate the verification results, run kani verify-std -Z
unstable-options "path/to/library" -Z function-contracts -Z
mem-predicates --harness ptr::non_null::verify This will run both
harnesses. All default checks should pass:

```
SUMMARY:
 ** 0 of 1622 failed

VERIFICATION:- SUCCESSFUL
Verification Time: 0.3814842s

SUMMARY:
 ** 0 of 1780 failed (1 unreachable)

VERIFICATION:- SUCCESSFUL
Verification Time: 0.44192737s

Complete - 2 successfully verified harnesses, 0 failures, 2 total.
``` 

### Clarifying Questions 
The proof now only handles the array with a fixed size and uses a random
element in the arr for subtraction. The element is i32 type. Is this ok
for the current stage? Or maybe we need to consider other types such as
i64, etc and maybe change the arr to a bigger size?

---------

Co-authored-by: OwO <owo@OwOs-MacBook-Pro.local>
Co-authored-by: Qinyuan Wu <qinyuanw@andrew.cmu.edu>
Co-authored-by: Carolyn Zech <cmzech@amazon.com>
Co-authored-by: Zyad Hassan <88045115+zhassan-aws@users.noreply.github.com>
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-type-system Area: Type system
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@froystig @pcwalton