Updating the roadmap page on the wiki.

[abhi18av]

Hey, crystal team :)

This is a not a feature request or an issue, just a reminder to update the roadmap as laid out on the wiki section. Feel free to close this.

I see that much work has been done since then, perhaps some of the enlisted tasks have been completed?

[RX14]

The roadmap looks pretty up-to-date to me. It's concerning to me that we've made little progress on the roadmap since February. The exception being windows support which isn't merged but we have a plan at least.

Edit: oh and Random has been redesigned since February, I guess that can be ticked off.

[ysbaddaden]

Most of the roadmap is still valid. Goals are large and can't be reached in only a few months. For example "review the type system" or "review the language syntax & design"...

I ticked Random and SecureRandom, since most of the work has been done recently (and #4536 should be merged). I didn't tick OpenSSL, though the only thing missing are bindings for certificates.

I started working on adding nanoseconds precision to Time and Time::Span, but it's not easy task (instead of a single Int64 ticks, we must deal with an Int64 + Int32).

Windows support is ongoing and a huge task.

[RX14]

@ysbaddaden I like go's idea of adding a monotonic clock value to Time as well but I don't think there's any way to fit that in 128 bits (with TZ offset). Maybe if we reduced tick precision for Time but added a monotonic nanosecond precision clock as well that would be enough.

[akzhan]

Go time is (sec Int64, nsec Int32, loc Location(ref)) struct.

And I think that trying to fit it into 128 bit is not the target.

[asterite]

I wouldn't worry at all about the size of the Time struct. I'd focus on having the features we'd like, and correctness before performance.

[RX14]

@akzhan Not in master: https://github.com/golang/go/blob/b0d592c3c9a356b661c2d6bb958528f2761d821e/src/time/time.go#L116.

[mverzilli]

Closing, @ysbaddaden and @RX14 properly answered the question.