Nikolay Artamonov

@987Nabil agree to have only simplified `ZIO.log*` methods that works with strings only. We can make customized methods ourselves. But it should be some way to install custom loggers system-wide...

Unfortunately addition of the new method to trait `Accessible` breaks binary compatibility for Scala 2.11. I think it's because of different encodings of traits in 2.11 and 2.12+, see lightbend/mima#205.

@adamgfraser I've retargeted the enhancement for ZIO 2.x in #6369. I agree with @guizmaii, many users of ZIO (including me) will not be able to migrate to 2.x any time...

Release notes for RC19 mention `TestAspect.only` was implemented but actually it have been deleted from library in #3696. It' sad... Should we re-open the issue? It's very helpful combinator, at...

@ziggystar as a workaround you can use functional components and `useState` hook: ```scala object State { def initialState: State = ??? } sealed trait State case class S1() extends State...

I'm relatively layman in the world of FP, but at my work we extensively use ZIO and othen FP libs to drive our stuff. So, in my opinion (it may...

I use 1.0.0.0-RC24. Yes, `contentType` and `HeaderValues.textPlain` both return `CharSequence`, but they are not comparable however: ```scala import zhttp.http._ val rs = Response() .updateHeaders(_.addHeader(HeaderNames.contentType, HeaderValues.textPlain)) rs.contentType == Some(HeaderValues.textPlain) // evals...

Or even better, what if we will specialize existing `equalTo` combinator to properly handle `CharSequence`s? Something like: ```scala final def equalTo[A, B](expected: A)(implicit eql: Eql[A, B]): Assertion[B] = Assertion.assertion("equalTo")(param(expected)) {...

+1 about cryptic meaning of `!!`, in my opinion `Root` was clearer. Indeed IDEA considers `!!` as a pattern variable, this adds to the misunderstanding: 

> The Windows problem is now fixed. See #554 @demarey When will the new version of pharo-launcher be released? I've just downloaded brand new Pharo 10 from the site and...