cask VS refined

I want to just block as if there's no tomorrow, no effects / hardcore FP (maybe only something like https://github.com/softwaremill/ox), what would you use? E.g. for http server / db / json ?https://github.com/com-lihaoyi/cask ?

There's the Li Haoyi's ecosystem of tools and libraries that's fun to hack on, has a low entry-bar (with a design philosophy of using the least complex abstractions for the job), and has few libs like requests and cask that may appeal to those liking some python minimalism. That's not the fastest way to learn hardcore FP, that's not the worst either.

Wonder if anyone uses: https://github.com/com-lihaoyi/cask

Is play-framework a strong requirement? If not, you might have an easier time building a simple API and serializing JSON with the lihaoyi ecosystem, namely cask as the microframework and uPickle/uJson.

For people who want to get their feet wet with Scala, I highly recommend Cask and the rest of what some people affectionately call “the Singapore stack,” in honor of Li Haoyi, its developer. He emphasizes tasteful use of Scala features with an emphasis on API ergonomics. All of his work is a joy to use.

The documentation points to a pretty outdated example. Can you try with the latest 0.8.3 release?

If you want something really easy and simple, have a look at cask: https://com-lihaoyi.github.io/cask/

Best I can do is Cask: https://com-lihaoyi.github.io/cask/ 😅

Scala has quite good support for refined types across multiple libraries. A solution using the refined library might look something like

Does the Refined library for Scala (at https://github.com/fthomas/refined; "eu.timepit" %% "refined") work in Scala 3? Does it work differently?

I'm trying to create a poor man version of refined types implementation with a simple validation of string content and check the return type via Implicit evidence on another function. It seems that the type got erased after it got returned from the check

Scala likes to do design-by-contract on the type level. You encode your pre- and post- conditions into types. Libraries like iron (scala 3) https://github.com/Iltotore/iron and refined (scala 2) https://github.com/fthomas/refined allow you to do all that without throwing any exceptions and they can even enforce some simple predicates at compile time.

Annotation is not the only way (and probably not the best IMHO) to do refined types. You might be interested in Iron in Scala 3 or Refined in Scala 2/3.

I think the way you model problems in Ada is superficially similar to refined types you find in some functional languages (e.g. Scala).

In one respect, nothing. You’re right. Even given refinement types as in Haskell or Scala, there is indeed a necessarily-partial function (refineV in Scala) to refine a value to its refinement type.

Perhaps refined would help you? It lets you set constraints (i.e. "rules") for values / types. You get compile-time enforcement for constants and fallible methods for runtime values (i.e. Either[Error, RefinedValue]).

This is more or less how derivation works when you want to use something like Refined types (it exposes Validate[Type, Refinement] typeclass if I remember correctly). Enumeratum exposes Enum[A], and newtypes expose Coercible[From, To].

You will probably be interested into Iron or Refined.