2.0.0-RC6: AssertionM gone

AssertionM is gone and neither in the migration guide nor in the 2.0.0-RC6 release notes there’s a mention on how to migrate. Please update the docs and/or release notes - thx!

[adamgfraser]

@boniface That is very fair feedback. Appreciate it. We try to do that but given how close we are to a final release there doesn’t seem to be much value in deprecating things we will need to immediately delete.

At least my experience in upgrading libraries for the latest release candidate was that it was quite straightforward as almost all the changes were relatively mechanical and IO.someMethod can always be replaced with ZIO.someMethod and so on, but understand there is some work involved and that isn’t completely automated if you moved to a previous ZIO release candidate.

Thank you for bearing with us as we get to the final version here. I think at least the experience of everyone I have worked with is ZIO 2 is dramatically nicer to use than ZIO 1, so hopefully you and your team find it was worth the wait.

[ya-goodfella]

2.0.0-RC6 is really an “ouch” release for my team. Even zio.IO.fromfuture is gone and replaced with zio.ZIO.fromfuture, and I can understand the reason behind that, ergonomically. However, I would expect this straight deletion of operators to be managed in a usual methodical way that is well known to us all; deprecation and then deletion, especially for a Release Candidate (RC). I would be okay with straight deletions happening at the milestones version. RCs create a certain expectation and signal to a lot of us to start moving our codebases to the upcoming versions, and these straight deletions really catch us off guard. A consideration in this direction will be greatly appreciated.

Well, scalafix would fix that for you automatically. 😃