[Issue 5233] [patch] std.range.put accepts *any* element type when putting to an array.

https://issues.dlang.org/show_bug.cgi?id=5233 monarchdo...@gmail.com changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Issue 5233] [patch] std.range.put accepts *any* element type when putting to an array.

https://issues.dlang.org/show_bug.cgi?id=5233 --- Comment #11 from monarchdo...@gmail.com --- AFAIK, with my last put pull about 6 months ago, all issues (that I know of) are resolved. @ Andrei Alexandrescu : You are assigned to this issue. Is there anything left outstand IRT put? If not, can

[Issue 5233] [patch] std.range.put accepts *any* element type when putting to an array.

https://issues.dlang.org/show_bug.cgi?id=5233 --- Comment #12 from Andrei Alexandrescu and...@erdani.com --- (In reply to monarchdodra from comment #11) AFAIK, with my last put pull about 6 months ago, all issues (that I know of) are resolved. @ Andrei Alexandrescu : You are assigned to this

[Issue 5233] [patch] std.range.put accepts *any* element type when putting to an array.

http://d.puremagic.com/issues/show_bug.cgi?id=5233 monarchdo...@gmail.com changed: What|Removed |Added CC||monarchdo...@gmail.com ---

[Issue 5233] [patch] std.range.put accepts *any* element type when putting to an array.

http://d.puremagic.com/issues/show_bug.cgi?id=5233 --- Comment #9 from Rob Jacques sandf...@jhu.edu 2012-03-19 09:56:04 PDT --- (In reply to comment #8) I think the patch has diverged from the intended charter of put, as mentioned in the pull request. I am misunderstanding something. In the

[Issue 5233] [patch] std.range.put accepts *any* element type when putting to an array.

http://d.puremagic.com/issues/show_bug.cgi?id=5233 --- Comment #8 from Andrei Alexandrescu and...@metalanguage.com 2012-02-18 10:40:03 PST --- I think the patch has diverged from the intended charter of put, as mentioned in the pull request. -- Configure issuemail:

[Issue 5233] [patch] std.range.put accepts *any* element type when putting to an array.

http://d.puremagic.com/issues/show_bug.cgi?id=5233 Rob Jacques sandf...@jhu.edu changed: What|Removed |Added Keywords||pull --- Comment #7

[Issue 5233] [patch] std.range.put accepts *any* element type when putting to an array.

http://d.puremagic.com/issues/show_bug.cgi?id=5233 --- Comment #5 from Rob Jacques sandf...@jhu.edu 2011-04-02 22:22:59 PDT --- Patch version 6. *sigh* Naturally, new ideas come immediately after my previous post. *** API Addition *** ER or R's ElementEncodingType allows user-defined-types to

[Issue 5233] [patch] std.range.put accepts *any* element type when putting to an array.

http://d.puremagic.com/issues/show_bug.cgi?id=5233 --- Comment #4 from Rob Jacques sandf...@jhu.edu 2011-04-01 22:01:14 PDT --- Patch version 5. *** API Addition *** Optional template boolean parameter asArray. If true, put bypasses testing r.put(e), r.put(e[]), r(e) and r(e[]). This allows

[Issue 5233] [patch] std.range.put accepts *any* element type when putting to an array.

http://d.puremagic.com/issues/show_bug.cgi?id=5233 --- Comment #3 from Rob Jacques sandf...@jhu.edu 2011-03-15 22:22:43 PDT --- Patch version 4. (DMD 2.052, Line 272+) * Removed some debug code that was accidentally included in the last version * Refactored and reformatted * Fixed/added support

[Issue 5233] [patch] std.range.put accepts *any* element type when putting to an array.

http://d.puremagic.com/issues/show_bug.cgi?id=5233 Andrei Alexandrescu and...@metalanguage.com changed: What|Removed |Added Status|NEW |ASSIGNED

[Issue 5233] [patch] std.range.put accepts *any* element type when putting to an array.

http://d.puremagic.com/issues/show_bug.cgi?id=5233 --- Comment #1 from Rob Jacques sandf...@jhu.edu 2010-11-18 12:02:54 PST --- An updated patch allowing char[]/wchar[] to be put into ubyte/ushort output ranges. void put(R, E)(ref R r, E e) { // BUG, adding template constraints result in a

[Issue 5233] [patch] std.range.put accepts *any* element type when putting to an array.

http://d.puremagic.com/issues/show_bug.cgi?id=5233 --- Comment #2 from Rob Jacques sandf...@jhu.edu 2010-11-18 13:23:19 PST --- *sigh* Patch version 3. Added support for putting an input range into an output range. Unit test: assert( isOutputRange(Appender!(ubyte[]),string) ); Patch: void