iron
refined
Our great sponsors
iron | refined | |
---|---|---|
20 | 16 | |
404 | 1,678 | |
- | - | |
8.3 | 8.6 | |
25 days ago | 8 days ago | |
Scala | Scala | |
Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
iron
-
Make Invalid States Unrepresentable
Scala has quite good support for refined types across multiple libraries. A solution using the refined library might look something like
- Y-at-il icy gens que creere son propre project open source?
-
Effect of Perceptual Load on Performance Within IDE in People with ADHD Symptoms
> The output you see is not generated by python.
Obviously, as running the code generates a very different output…
> It's generated by an external type checker.
I know.
But again, you didn't say that.
You said the above code "generates" this…
Maybe you've heard that by now somewhere: Words matter… ;-)
> The context is python. We're talking about python. I'm making a statement about python.
No, you made a statement about type checking. Here the full quote once again:
> The contents of a string can't be type checked and if all methods are defined this way on a class none of it can be checked.
Nothing in this statement is about Python.
All I did was just proving your words once again to be nonsense: You can statically dispatch (which involves static type checking!) just fine on strings. My (Scala) code is prove of this fact.
> There is literally nothing in my statement to indicate I'm making a general statement about type checking.
LOL. Do you actually know what you're writing? Once more:
> The contents of a string can't be type checked and if all methods are defined this way on a class none of it can be checked.
That's a general statement… It couldn't be even more general, actually.
> But I will say checking for the contents of a string is rare for a type checker to do. That is a general statement that is generally true.
Once again complete nonsense.
There are whole libraries doing more or less nothing else than handling singleton types.
Whole software layers utilize that! But I guess you never heard of static data validation…
https://github.com/Iltotore/iron
You have so little clue, but such a big mouth… That's so embarrassing.
A helpful tip: Stop spiting out maximally general claims (because these are almost always wrong!), and think about what you're actually writing.
What's in your fantasy, or what you "may have meant" is irrelevant!
> The guy made factually incorrect statements and so did you.
That's exactly what I'm talking about: You're a severe DK victim as it seems…
> It's just true that he's wrong.
No, actually you are wrong with almost every claim, like I've proven now several times. And this nonsense still didn't stop… Oh, boy!
> people shouldn't get worked up about someone else identifying a mistake.
Think about that once again. Especially in the context that it's you who is wrong here with almost everything you say.
And no, nobody is "pedantic". It only gets quite unrealistic that someone who doesn't even get banal prose straight would be able to write any code. Because the computer is actually very pedantic. And after production is on fire you can't just come to your boss and excuse yourself with "but I've meant this differently, just the stupid computer did again not understand what I've meant".
But to be honest this would actually explain:
> I've likely worked for more companies then you in the last 5 years or so due to my personality. I don't stay at one place for long.
I have some suspicions to why you don't stay anywhere for long… And yes, that would be indeed related to personality…
-
Does the fthomas/refined library work differently in Scala 3?
You might want to check out Iron.
-
Iron updates: turning opaque types into value objects
And there is a beginner-friendly ticket: Add alias for True constraint and IronType[A, True]
- Iron v2.1.0 is out!
- Design by contract - Preconditions and Postconditions - I'm really amazed with Scala.
-
Restrict uses of annotation in Scala
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.
- Iron v2.0.0 Is Out
-
Iron v2.0.0 is out 🎉
The second major version of Iron is out, featuring a complete rewrite on top of better foundations.
refined
-
Make Invalid States Unrepresentable
Scala has quite good support for refined types across multiple libraries. A solution using the refined library might look something like
-
Does the fthomas/refined library work differently in Scala 3?
Does the Refined library for Scala (at https://github.com/fthomas/refined; "eu.timepit" %% "refined") work in Scala 3? Does it work differently?
-
Type erased on implicit evidence check
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
-
Design by contract - Preconditions and Postconditions - I'm really amazed with Scala.
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.
-
Restrict uses of annotation in Scala
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.
-
Cross-Training to Ada - which are the best languages to begin from?
I think the way you model problems in Ada is superficially similar to refined types you find in some functional languages (e.g. Scala).
-
Can types replace validation?
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.
-
Help me break the fourth wall
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]).
-
Simple, Naïve, and Wrong: More than you wanted to know about Scala Case Classes
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].
-
Opinions on implementing traits for validation with the help of a companion object
You will probably be interested into Iron or Refined.
What are some alternatives?
scala-3-migration-guide - The Scala 3 migration guide for everyone.
Shapeless - Generic programming for Scala
iron-cats-example - An example project using Iron & Cats
Records for Scala - Labeled records for Scala based on structural refinement types and macros.
Troy - Type-safe and Schema-safe Scala wrapper for Cassandra driver
Cassovary - Cassovary is a simple big graph processing library for the JVM
longevity - A Persistence Framework for Scala and NoSQL
Ammonite-Ops - Scala Scripting
adhd-study
scala-newtype - NewTypes for Scala with no runtime overhead
scala-redis - A scala library for connecting to a redis server, or a cluster of redis nodes using consistent hashing on the client side.
Scalaz - Principled Functional Programming in Scala