Add HtmlTag#withSelf, restore debounce example

[armanbilge]

Closes #132.

[armanbilge]

This is extremely annoying. Another workaround is to do:

input { self =>
  Tuple1(onInput --> (_.evalMap(_ => self.value.get).through(emailCh.sendAll)))
}

I'm going to try and minimize and report a compiler bug.

[armanbilge]

• Method overload with mismatched type chosen over generic overload scala/scala3#16737

[2chilled]

Seems like there's still work to do in regards to implementing overloads soundly, even in Scala 3. To this day, I've always avoided them without missing too much.

[armanbilge]

To this day, I've always avoided them without missing too much.

Yes, that is often good practice. Do you think we should do that here? We can add it as an alternative API e.g.

input.withSelf { self =>
  onInput --> (_.evalMap(_ => self.value.get).through(emailCh.sendAll))
}

I think Laminar might call it withContext.

[2chilled]

I'd absolutely prefer that, yes. These types of bugs are super annoying, especially for non expert Scala users. In my experience it's best to even disable all nasty features that can be somehow disabled. At work, we use the strictest scalac 2 settings together with nearly all of https://www.wartremover.org/, and everyone is super happy with that. Furthermore, we still avoid Scala 3 there, because there are a bunch of strict flags not implemented (yet?).

[2chilled]

Ah and withSelf is a good name in my subjective eyes :)

[armanbilge]

Great, I'll add that!

because there are a bunch of strict flags not implemented (yet?).

Good news, many new strict flags are arriving in Scala 3.3.0 :)

• [Semester Project] Add new front-end phase for unused entities and add support for unused imports scala/scala3#16157

[armanbilge]

Not to second guess 😅 maybe another option is fromSelf. But withSelf is good. I think 😅

[armanbilge]

Yeah, overloads are bad 😓

trying a different solution

[armanbilge]

Seems like there's still work to do in regards to implementing overloads soundly, even in Scala 3.

Yeah, seems like what I was trying to do here was an unsupported behavior according to scala/scala3#16737 (comment) 😅