Thread overview
[Issue 11281] New: Range violation for associative array with Nullable!SysTime values
Oct 16, 2013
Mario Kroeplin
Oct 19, 2013
Kenji Hara
Oct 20, 2013
Kenji Hara
October 16, 2013
http://d.puremagic.com/issues/show_bug.cgi?id=11281

           Summary: Range violation for associative array with
                    Nullable!SysTime values
           Product: D
           Version: D2
          Platform: x86
        OS/Version: Linux
            Status: NEW
          Severity: regression
          Priority: P2
         Component: DMD
        AssignedTo: nobody@puremagic.com
        ReportedBy: kroeplin.d@googlemail.com


--- Comment #0 from Mario Kroeplin <kroeplin.d@googlemail.com> 2013-10-16 04:33:55 PDT ---
With dmd 2.064 (beta 1), the following code results in a Range violation:

unittest
{
    import std.datetime;
    import std.typecons;

    Nullable!SysTime[string] aa = null;

    aa["foo"] = Clock.currTime;
}

core.exception.RangeError: Range violation

With dmd 2.063.2, the unittest passes.

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



--- Comment #1 from Kenji Hara <k.hara.pg@gmail.com> 2013-10-19 11:55:14 PDT ---
Hmm. RangeError does not occur with 2.064 beta2 and git-head. http://forum.dlang.org/thread/52605C84.6010109@walterbright.com

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


Kenji Hara <k.hara.pg@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED


--- Comment #2 from Kenji Hara <k.hara.pg@gmail.com> 2013-10-19 23:40:58 PDT ---
OK, confirmed. The root cause of this issue is mostly same with bug 10357, and it has been fundamentally fixed from 2.064beta2.

-- 
Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email
------- You are receiving this mail because: -------