mikros/rust - rust - Gitea.pterpstra.com

mikros/rust

Fork 0

Commit Graph

Author	SHA1	Message	Date
Jonathan Turner	70ce90c320	Move 'doesn't live long enough' errors to labels	2016-08-17 15:24:42 -07:00
Felix S. Klock II	0fa1c1662f	Fallout to compile-fail tests. This change is worrisome to me, both because: 1. I thought the rules in RFC 599 imply that the `Box<Trait>` without `'static` in the first case would expand to the second case, but their behaviors here differ. And, 2. The explicit handling of `'static` should mean `dropck` has no application here and thus we should have seen no change to the expected error messages. Nonetheless, the error messages changed.	2015-05-08 16:08:59 +02:00
Niko Matsakis	5a39a0d266	To handle more complex cases, modify the deferred call handler to be specialized to closures, and invoke them as soon as we know the closure kind. I thought initially we would need a fixed-point inference algorithm but it appears I was mistaken, so we can do this.	2015-02-01 06:13:06 -05:00

Author

SHA1

Message

Date

Jonathan Turner

70ce90c320

Move 'doesn't live long enough' errors to labels

2016-08-17 15:24:42 -07:00

Felix S. Klock II

0fa1c1662f

Fallout to compile-fail tests.

This change is worrisome to me, both because:

1. I thought the rules in RFC 599 imply that the `Box<Trait>` without `'static`
   in the first case would expand to the second case, but their behaviors
   here differ.  And,

2. The explicit handling of `'static` should mean `dropck` has no application
   here and thus we should have seen no change to the expected error messages.
   Nonetheless, the error messages changed.

2015-05-08 16:08:59 +02:00

Niko Matsakis

5a39a0d266

To handle more complex cases, modify the deferred call handler to be

specialized to closures, and invoke them as soon as we know the
closure kind. I thought initially we would need a fixed-point
inference algorithm but it appears I was mistaken, so we can do this.

2015-02-01 06:13:06 -05:00

3 Commits