Passing around phantom typed proof witnesses as a revolutionary system design idiom that will change the world is peak googler.
=> More informations about this toot | More toots from pkhuong@discuss.systems
@pkhuong Is there some additional context I am missing for this post?
=> More informations about this toot | More toots from zwarich@hachyderm.io
@zwarich https://lwn.net/Articles/995814/ "this can reshape how we do software engineering"
=> More informations about this toot | More toots from pkhuong@discuss.systems
@pkhuong @zwarich I saw the video (all the RustConf videos were uploaded yesterday it looks like) and I had a pretty similar reaction to you. This kind of thing would probably be a stronger sell to non-Rust or non-typed-FP programmers. I can see it being a strong sell to people who are used to traditional systems languages with very limited type systems.
=> More informations about this toot | More toots from pervognsen@mastodon.social
@pkhuong @zwarich The specific trick in his talk where there's an unsafe LockBefore trait but a safe impl macro is kind of neat, I thought. It relies on the fact that trait resolution for conditional trait impls guarantees that the lock order is acyclic. (Although I admit I didn't think through all the details of that claim, so there could be problems with it.)
=> More informations about this toot | More toots from pervognsen@mastodon.social
@pervognsen @pkhuong As someone pointed out on Reddit, the solution (at least as described in the talk) also forbids acyclic diamonds: https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=2d929295ddef42aca19cad7309f2f7b5
=> More informations about this toot | More toots from zwarich@hachyderm.io This content has been proxied by September (3851b).Proxy Information
text/gemini