Things are not going well...
However, these statistics functions are used depending on a case well.
In addition, I think that it is not overengineering about only
dstats.summary when I watch recent Phobos.
I think it seems to be worth being included in Phobos.
It seems to be necessary to look at the state for a while.
--
SHOO
(2010/11/18 22:49), David Simcha wrote:
Others have suggested this in the past. There are/were a few major
things holding it up:
1. While I feel that dstats.summary has about the right level of
complexity/engineering for a third-party statistics lib, I'm a little
worried that it's overengineered for a standard library module.
2. The brokenness of alias this. I designed the hierarchy of different
summary-calculating output ranges to rely heavily on alias this. The
relevant bugs may have been fixed recently, in 2.050. I'll have to check.
3. A bunch of stuff uses TempAlloc for its temporary scratch space. I'd
like to keep it that way for efficiency, but it's hard to put TempAlloc
into Phobos given that the issue of GC scanning *still* isn't solved.
One solution to these problems is to just move the more basic stuff over
to Phobos and publicly import it from dstats.summary.
On 11/18/2010 8:00 AM, SHOO wrote:
BTW, I want statistical functions in Phobos. For example,
dstats.summary looks good. Is there the plan to introduce such functions?
--
SHOO
_______________________________________________
phobos mailing list
[email protected]
http://lists.puremagic.com/mailman/listinfo/phobos
