Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
Fabio Labella
@SystemFw
so no shame at all
but once you actually fully understand what it gives you, it's really really hard to go back
Tim McIver
@tmciver
Thanks once again for the info, I appreciate it!
Fabio Labella
@SystemFw
no worries :)
Adelbert Chang
@adelbertc
@SystemFw you should start talking mysteriously when answering questions
talk in proverbs
Fabio Labella
@SystemFw
I'm saying that for when my beard turns grey
Cody Allen
@ceedubs
@coltfred iirc there is a CatsEquality trait that is mixed into CatsSuite that does this. It took me 2.7 years to figure out how to make it work.
Rob Norris
@tpolecat
Pls explain.
What predicates use it?
Cody Allen
@ceedubs
If you use should ===
This should probably be documented...
Rob Norris
@tpolecat
I wish there were a way to turn off the matchers that use universal equality.
Scratch that.
I wish matchers would die in a garbage fire.
Having to decode matcher syntax into the underlying boolean expressions is a ridiculous way to spend my time.
And thus far I have apparently been wrong 100% of the time because I was using shouldBe or something like that, which wasn't using Eq.
nafg
@nafg
you're talking about scalatest?
Just don't mix in Matchers or whatever
Rob Norris
@tpolecat
Well I'm using CatsSuite to be consistent with what cats does.
Another thing I don't want to waste time on is figuring out what test dialect to use.
nafg
@nafg
yeah, I just use FunSuite, I think it gets out of the way the most
when I use scalatest
Of course, wasting time figuring out what testing framework to use is another thing one can complain about ;)
Rob Norris
@tpolecat
Yeah CatsSuite mixes in matchers but I guess I don't have to use them.
Well my biggest complaint is that an assertion is a side-effect in every test framework which makes test code terrible.
nafg
@nafg
maybe it shouldn't mix it in, sounds like a fun topic to debate :D
Rob Norris
@tpolecat
Really I can complain indefinitely about the testing situation in Scala.
nafg
@nafg
Yeah, that's a broader issue
Rob Norris
@tpolecat
Maybe I should start a podcast.
nafg
@nafg
Have you seen https://github.com/tek/xpct ?
You definitely should, scala needs more :)
Rob Norris
@tpolecat
Huh, no I haven't seen that.
nafg
@nafg
haven't used it, but it's by the author of the Splain compiler plugin and I was browsing his repos
Rob Norris
@tpolecat
Looks interesting. Edmund is writing one too.
nafg
@nafg
Is that why he's been so silent on Gitter lately? :D
Rob Norris
@tpolecat
He quit most of typelevel and scala/scala so he's less visible.
nafg
@nafg
:(
Michael Pilquist
@mpilquist

Maybe I should start a podcast.

@tpolecat: Yes!

nafg
@nafg
At a minimum, you could do an episode on @agbell's https://corecursive.com/
The entire episode could be about testing gripes :laughing:
Rob Norris
@tpolecat
I got an email from him a few hours ago, reminding me that I never responded to his email from a month ago.
But yes, I should do that.
Harmeet Singh(Taara)
@harmeetsingh0013
Hey channel, I am new to scala-cats, I have one quick question, why we require Foldable even scala core collections have method fold, foldLeft and foldRight?
Loránd Szakács
@lorandszakacs

folks, if my main "method" is ultimately described as a Task[Unit] it is a sane thing to just mainTask.runSyncUnsafe(Duration.Inf), at the end of the world right? Or is there a better way of running your final app?

Until recently I had cats.effect.IO, but for various reasons wound up changing it to monix Task, and w/ IO I just did the mainIO.unsafeRunSync — worked fine.

Adelbert Chang
@adelbertc
yeah
you generally want to just do it once at the "end of the world"
which is main
Luka Jacobowitz
@LukaJCB
@harmeetsingh0013 can you rephrase your question? I'm not sure I understand (: