Consider my +1 for Source/Sink more as a -1 for Port/Chan. I don't really care what it ends up as so long as I don't have to look up which is which every time. Sender/Receiver wfm.
As far as concerns about the proposal itself, my only remaining issue is that Chan isn't a trait and so the actual chan type you use can't be arbitrarily swapped without changes throughout a code base. The morphing channel partially addresses this, but doesn't really accommodate things like wrapped channels or switching to the unbounded or bounded alternatives. I understand there are drawbacks to making it a trait, though, so this isn't a counter proposal, just a lament. On Thursday, January 23, 2014, Benjamin Striegel <[email protected]> wrote: > If we're going to quibble over names we might as well call the types > Sender and Receiver. > > Really though, EVERYONE is fine with the proposed semantics from the > original thread? Really? Speak up if you have anything valuable to add that > isn't bikeshedding! :) > > > On Thu, Jan 23, 2014 at 11:13 PM, don > <[email protected]<javascript:_e({}, 'cvml', > '[email protected]');> > > wrote: > >> Hi, as a not contributing listen-in, >> >> i would like to voice that source and sink share the same initial and >> therefore source and drain might be more useful. >> >> I hope i didn't offend by voicing my opinion, >> keep up the good work! >> >> Regards Don >> >> >> Am 24.01.2014 04:54, schrieb Brandon Sanderson: >> >>> I would expect Channel::new() to create a channel object that either >>> lets me send and receive, or lets me get a source and sink to send and >>> receive with. Borrow rules may prevent this, but my point is that >>> Channel::new() would generally be expected to return a struct, and not a >>> tuple. >>> >>> On Jan 23, 2014 7:29 PM, "Benjamin Striegel" >>> <[email protected]<javascript:_e({}, 'cvml', >>> '[email protected]');> >>> <mailto:[email protected] <javascript:_e({}, 'cvml', >>> '[email protected]');>>> wrote: >>> >>> This all seems a bit silly. A channel *is*, conceptually, a tuple of >>> a sender and a receiver. If I call Chan::new(), that's what I expect >>> to get. And Chan::open() doesn't map to anything that's as intuitive. >>> >>> Is naming really all that's left to argue about? How does everyone >>> feel about the semantics of the proposal? >>> >>> >>> On Thu, Jan 23, 2014 at 10:20 PM, Strahinja Markovic >>> <[email protected] <javascript:_e({}, 'cvml', >>> '[email protected]');><mailto: >>> [email protected] <javascript:_e({}, 'cvml', '[email protected]');>>> wrote: >>> >>> >>> On Thu Jan 23 2014 at 7:18:11 PM, Tony Arcieri >>> <[email protected] <javascript:_e({}, 'cvml', >>> '[email protected]');> <mailto:[email protected] <javascript:_e({}, >>> 'cvml', '[email protected]');>>> wrote: >>> >>> I have a crazy idea... >>> >>> Channel::open() >>> >>> >>> That's a better name for the function, agreed. >>> >>> >>> https://lh3.ggpht.com/-WpuYGqCEHDg/UBznzaqReKI/ >>> AAAAAAAAB_0/0Vc8_mnnhqw/s1600/mind-blown.gif >>> >>> -- >>> Tony Arcieri >>> >>> >>> _______________________________________________ >>> Rust-dev mailing list >>> [email protected] <javascript:_e({}, 'cvml', >>> '[email protected]');> <mailto:[email protected]<javascript:_e({}, >>> 'cvml', '[email protected]');> >>> > >>> >>> https://mail.mozilla.org/listinfo/rust-dev >>> >>> >>> >>> _______________________________________________ >>> Rust-dev mailing list >>> [email protected] <javascript:_e({}, 'cvml', >>> '[email protected]');> <mailto:[email protected]<javascript:_e({}, >>> 'cvml', '[email protected]');> >>> > >>> >>> https://mail.mozilla.org/listinfo/rust-dev >>> >>> >>> >>> _______________________________________________ >>> Rust-dev mailing list >>> [email protected] <javascript:_e({}, 'cvml', >>> '[email protected]');> >>> https://mail.mozilla.org/listinfo/rust-dev >>> >>> _______________________________________________ >> Rust-dev mailing list >> [email protected] <javascript:_e({}, 'cvml', '[email protected]');> >> https://mail.mozilla.org/listinfo/rust-dev >> > >
_______________________________________________ Rust-dev mailing list [email protected] https://mail.mozilla.org/listinfo/rust-dev
