Emil Kantis

I dont get it.. It's failing when we have different values, but passing when the same number? Feels like it should be considered fine then to compare ints and longs?

``` test("dummy 1") { 6L shouldBe 6 } --> pass test("dummy 2") { val y: Int = 6 6L shouldBe y } --> pass ```

Awesome :) do you have any hunch as to why the tests fail on just IC-212? 🤔

> Nope, perhaps it's just not setup right, that was a recent addition to the build matrix. Doh, so I just had to update those plugin.xml files 😂 sorry. Should...

@sksamuel thx for re-opening. I haven't gotten much feedback on this one so I'm still unsure if it has acceptable performance impact. I sometimes felt IntelliJ got a bit sluggish...

I'm not sure if this is something Kotest should be concerned with? In our case (with the gradle plugin spec), I think it's a [gitattribute](https://github.com/kotest/kotest/blob/master/.gitattributes#L1) which forces LF line-endings even...

> Fair enough - it's not required, and there are workarounds. It's just annoying when tests depend on the machine they're run on, and the original author might not realise...

> I like the last suggestion too as we could have multiple options like trim and case insensitive I like it too. Perhaps the pattern could also be re-used for...

> 2. how nasty is CSV parsing? in its simple version it seems trivial, but I can imagine there are a lot of hidden surprises. isn't it something we can...

There's a chance we'll try to get https://github.com/kotest/kotest/pull/3264 out tonight, so disabled auto-merge for now.