Daniele Margutti

same here

@r-plus I think its the better choice; I've changed it here: https://github.com/malcommac/Hydra/commit/b9568eff1dc799d7c25a211d529ef1058780b787.

Are you talking about macOS compatibility? What kind of error you got?

should be fixed in 7.0

fixed in 7.0.0

`calendar` is defined as let and assigned at init time so it cannot be change further.

yeah, you are right. So what do you think is the best approach? We can return a copy of the calendar var and keep it private. Any other solution?

I'm a bit afraid to make another set of classes where the only scope is to avoid this issue; we will end with a big library of "non necessary things"....

yeah sure :) btw I can't see benefits; at the start of this project my idea is to completely hide the cocoa framework behind and make something with new structs...

@Hout We are using this for our NSDateFormatter object too!