I think ClosedRange. Also there should be support for floating types.
> On Sep 8, 2017, at 12:34 PM, Alejandro Alonso via swift-evolution > <[email protected]> wrote: > > Range support is something that came up, and I think it’s a great idea as > well. My question now is do we support both `CountableRange` and > `CountableClosedRange`? > >> On Sep 8, 2017, 12:08 PM -0500, Shawn Erickson <[email protected]>, wrote: >> It would be nice to leverage range support instead of a start and end value >> IMHO. >>> On Fri, Sep 8, 2017 at 9:52 AM Alejandro Alonso via swift-evolution >>> <[email protected]> wrote: >>> Hello swift evolution, I would like to propose a unified approach to >>> `random()` in Swift. I have a simple implementation here >>> https://gist.github.com/Azoy/5d294148c8b97d20b96ee64f434bb4f5. This >>> implementation is a simple wrapper over existing random functions so >>> existing code bases will not be affected. Also, this approach introduces a >>> new random feature for Linux users that give them access to upper bounds, >>> as well as a lower bound for both Glibc and Darwin users. This change would >>> be implemented within Foundation. >>> >>> I believe this simple change could have a very positive impact on new >>> developers learning Swift and experienced developers being able to write >>> single random declarations. >>> >>> I’d like to hear about your ideas on this proposal, or any implementation >>> changes if need be. >>> >>> - Alejando >>> >>> _______________________________________________ >>> swift-evolution mailing list >>> [email protected] >>> https://lists.swift.org/mailman/listinfo/swift-evolution > _______________________________________________ > swift-evolution mailing list > [email protected] > https://lists.swift.org/mailman/listinfo/swift-evolution
_______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
