A by-based delegation notation

IntroductionIn a recent lang design meeting Petrochenkov outlined a design for delegation based on a new reuse keyword. I unfortunately had to drop off early because of a work conflict, so unfortunately I couldn’t participate in the discussion. I've been thinking a little more about delegation since. Though I like the idea of delegation and the scope at which it's applied, I feel like the reuse proposal isn't quite where it needs to be yet. Kotlin’s by keyword (“provided by”) also provides delegation, and I think it is closer to what a Rust feature should feel like: For traits you’d use impl..for..by (“trait impl foo is provided by bar”) For impl blocks you'd use impl..by (“inherent impl is provided by bar”) For individual methods you’d use fn..by (“function foo is provided by bar”) Usually I try to provide some degree of analysis and detail in my posts. But I'm quite short on time, so the best I can provide is a big list of translated examples from RFC 3530 to show you what I think…

Commenting on Bubbles has been removed. Why? If you want to talk about this post, write to the author, use the comments on their blog if it has them, or reply with a "RE:" post on your own blog. Suggestions? feedback@bubbles.town