D issues are now tracked on GitHub. This Bugzilla instance remains as a read-only archive.
Issue 21201 - let std.uuid.parseUUID accept input ranges whose elements are char or wchar, not just dchar
Summary: let std.uuid.parseUUID accept input ranges whose elements are char or wchar, ...
Status: RESOLVED FIXED
Alias: None
Product: D
Classification: Unclassified
Component: phobos (show other issues)
Version: D2
Hardware: All All
: P1 enhancement
Assignee: No Owner
URL:
Keywords: pull
Depends on:
Blocks:
 
Reported: 2020-08-27 11:43 UTC by Nathan S.
Modified: 2020-08-27 14:47 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description Nathan S. 2020-08-27 11:43:31 UTC
All characters of interest to `std.uuid.parseUUID` are ASCII so there is no reason it cannot work on a range of chars or wchars.
Comment 1 Dlang Bot 2020-08-27 11:47:53 UTC
@n8sh created dlang/phobos pull request #7607 "Fix Issue 21201 - let std.uuid.parseUUID accept input ranges whose elements are char or wchar, not just dchar" fixing this issue:

- Fix Issue 21201 - let std.uuid.parseUUID accept input ranges whose elements are char or wchar, not just dchar
  
  All characters of interest to std.uuid.parseUUID are ASCII so there is
  no reason it cannot work on a range of chars or wchars.

https://github.com/dlang/phobos/pull/7607
Comment 2 Dlang Bot 2020-08-27 14:47:59 UTC
dlang/phobos pull request #7607 "Fix Issue 21201 - let std.uuid.parseUUID accept input ranges whose elements are char or wchar, not just dchar" was merged into master:

- ef33b5352fc1ab551def7f342906b78b769c7bd0 by Nathan Sashihara:
  Fix Issue 21201 - let std.uuid.parseUUID accept input ranges whose elements are char or wchar, not just dchar
  
  All characters of interest to std.uuid.parseUUID are ASCII so there is
  no reason it cannot work on a range of chars or wchars.

https://github.com/dlang/phobos/pull/7607