Creating a LocalTime from a TimeSpan should be simpler than it is

[GoogleCodeExporter]

While a TimeSpan really *isn't* a time of day, bits of the BCL treat it that 
way. It would be appropriate to have LocalTime.FromTimeSpan with appropriate 
caveats, and also LocalTime.FromTicksSinceMidnight and 
LocalTime.FromSecondsSinceMidnight. The current workaround is:

    LocalTime.Midnight + Period.FromTicks(ticks)

which is pretty nasty.

Original issue reported on code.google.com by jonathan.skeet on 11 Nov 2012 at 9:18

[GoogleCodeExporter]

This issue was closed by revision b292cacd4988.

Original comment by jonathan.skeet on 11 Nov 2012 at 9:47

• Changed state: Fixed

[GoogleCodeExporter]

Now we've got FromTicksSinceMidnight, using a TimeSpan is fairly 
straightforward:

    LocalTime time = LocalTime.FromTicksSinceMidnight(timeSpan.Ticks);

That's not terribly unpleasant, and it avoids polluting Noda Time with a 
conversion which isn't sensible for the *normal* meaning of TimeSpan.

Original comment by jonathan.skeet on 11 Nov 2012 at 9:48

[GoogleCodeExporter]

Original comment by malcolm.rowe on 30 Jan 2013 at 11:19

• Added labels: Type-Enhancement, Milestone-1.1.0