Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Conventionalizing stride semantics #184
added a commit
this pull request
Mar 11, 2016
Quite honestly, in its current state, this half of the split proposal did not have strong support
The problem it would be fixing would probably be better addressed by stepping back and re-thinking
-- Erica, who has been filling notebook pages with scribbles trying to think
I am impressed that you are taking the long view! I was thinking the same thing (especially in light of the new indexing model) but there’s no justification for rejecting the proposals for review at this point… unless you’re asking to withdraw them.
I actually do stand behind this proposal. I just worry that I'm fighting the wrong battle.
The other proposal's issues are clear: the math is demonstrably bad, and there are a bunch of
With this proposal, the main objection voiced by the community was this: the words I chose
I believe my semantics reflect natural ways to express the end progressions. These are end scenarios
At the same time, there are multiple issues with the current stride/interval/range system. I don't
Let me know what you think I should do.
I generally prefer to make a holistic analysis of an area of the library to making fixes that are likely to be obsoleted by something that looks very different. If you feel that there’s a better answer to be had with a broader analysis, I'd suggest we do that for Swift 4 or something. Otherwise, we should go ahead with the proposals as submitted.
I suspect there's a better answer to be had with a broader analysis.