import nettlesome.*
import gossamer.*
import contingency.*
import errorHandlers.throwUnsafely

println("hello")
println(t"[email protected]")
//println(EmailAddress.parse(t"[email protected]"))

Scala version being used is 3.5.0-RC1

1) Scastie

On scastie, it doesn't produce any output
https://scastie.scala-lang.org/bRgE1hMhTsysAgTxj8A0vA

2) local sbt project

On local sbt project, it produces this error:

[error] -- Error: /Users/propensive/work/gossamer/src/core/t.scala:29:57 ---------------
[error] undefined: gossamer.Interpolation.T.expand # -1: TermRef(TermRef(TermRef(TermRef(ThisType(TypeRef(NoPrefix,module class <root>)),object gossamer),Interpolation),object T),expand) at typer

This would allow Contextual to use the Text type in its API, and all its dependent projects.

Currently, Text values must be converted to Strings and matched against String patterns. Instead, it should be possible to match on them directly against patterns of the form, t"foo".

There's a bug in Scala's test coverage code which tries to cast an array to an immutable.Seq. Hopefully there's a way to avoid it.

This should be an opaque wrapper around StringBuilder, with typesafe methods.

Use a Cuttable typeclass parameterized on the type being cut, and the type used to do the cutting.

Gossamer has comprehensive text manipulation methods that work on Text instances, but not on other textlike types, such as in Escapade.

The current implementation is simplistic, and reuses Java's DecimalFormat (which it probably doesn't need to).

Currently, sorting is done using the default Ordering[String] instance. But it should be locale-dependent, and the locale should be made explicit.

For example, for French, we currently need to write something like:

val collator = Collator.getInstance(Locale.FRANCE)
given Ordering[String] = collator.compare(_, _)

The fluffy white clouds aren't distinctive enough.

The "fallback" of using toString seems to be applied when it ought to generically derive the appropriate typeclass instance.