March 19, 2012
http://d.puremagic.com/issues/show_bug.cgi?id=5233



--- Comment #9 from Rob Jacques <sandford@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 pull request, you mentioned that

> The intent of put(r, e) is to provide a universal generic interface for putting stuff into stuff using a unified syntax. As such, adding policies and options works against that charter. We're better off defining independent functions such as putArray etc.

However, put already contains policies for handling arrays, ranges, delegates, etc. All I've attempted to do, on that front, is to add all the variations (i.e. edge cases) on those concepts, so that generic code functions correctly.

The other feature I've added is some external control of those policies, a feature which is a interim measure until UFC is working.

-- 
Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
October 25, 2013
http://d.puremagic.com/issues/show_bug.cgi?id=5233


monarchdodra@gmail.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |monarchdodra@gmail.com


--- Comment #10 from monarchdodra@gmail.com 2013-10-25 00:15:58 PDT ---
Is any of this still relevent?

The unittest passes, all the implementations seem incredibly complicated...

In any case, since I also rolled out my own implementation: https://github.com/D-Programming-Language/phobos/pull/1569

I believe this further simplifies how put works, while consolidating the way it works. Most importantly though, it allows for "on the fly" transcoding.

-- 
Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
1 2
Next ›   Last »