<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">On Mar 3, 2014, at 12:04 AM, Chandler Carruth <<a href="mailto:chandlerc@google.com">chandlerc@google.com</a>> wrote:<br><div><blockquote type="cite"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; position: static; z-index: auto;"><div class=""><div><blockquote type="cite"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div>I was actually going to check in this, but I can post it for review if folks are worried.</div><div><br></div><div>My plan was to provide an implementation of std::iterator_range<T> and then provide 'F.arguments()' which returns it.</div>
</div></div></div></blockquote><br></div></div><div>Nice. What's the logic behind .arguments() vs .getArguments()? I don't have a strong opinion either way, but there should be rationale.</div></blockquote></div>
<br></div><div class="gmail_extra">In the best case 'get' doesn't really add any meaning, and in the worst case it is actively misleading</div></div></blockquote><div><br></div><div>It's getting the range though, just like Function::getArgumentList() returns the argument list.</div><br><blockquote type="cite"><div dir="ltr"><div class="gmail_extra">For example, you might iterate over operands, and assign through the iterator to mutate them.</div>
<div class="gmail_extra"><br></div><div class="gmail_extra">Really, these operate as range-views over some sequence. It seems particularly easy to teach foo_begin(), foo_end() -> foos() as well.</div></div>
</blockquote></div><br><div>That's a very objective-c thing to do :-), they use the pattern foo() and setFoo() for the getter and setter, respectively (and the naming is baked into the property model). I don't feel strongly against it, but we pretty consistently use the Java style 'get' prefix everywhere else.</div><div><br></div><div>-Chris</div></body></html>