#scala3 — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #scala3, aggregated by home.social.
-
I have written up a more detailed post about linear regression with #probula using grid approximation. The post focuses on:
- Explaining the example of linear regression in
probula(which is an internal DSL embedded in Scala 3) - Showing how grid approximation is implemented in
probula - Discussing how this implementation is tested and how is it used in testing of other #BayesianInference methods
Enjoy!
https://wasowski.dukla.ch/posts/2606-grid-approximation-with-probula/
#ProbabilisticProgramming #Bayesian #Inference #DataAnalysis #Scala #Scala3 #keep
- Explaining the example of linear regression in
-
I have written up a more detailed post about linear regression with #probula using grid approximation. The post focuses on:
- Explaining the example of linear regression in
probula(which is an internal DSL embedded in Scala 3) - Showing how grid approximation is implemented in
probula - Discussing how this implementation is tested and how is it used in testing of other #BayesianInference methods
Enjoy!
https://wasowski.dukla.ch/posts/2606-grid-approximation-with-probula/
#ProbabilisticProgramming #Bayesian #Inference #DataAnalysis #Scala #Scala3 #keep
- Explaining the example of linear regression in
-
I have written up a more detailed post about linear regression with #probula using grid approximation. The post focuses on:
- Explaining the example of linear regression in
probula(which is an internal DSL embedded in Scala 3) - Showing how grid approximation is implemented in
probula - Discussing how this implementation is tested and how is it used in testing of other #BayesianInference methods
Enjoy!
https://wasowski.dukla.ch/posts/2606-grid-approximation-with-probula/
#ProbabilisticProgramming #Bayesian #Inference #DataAnalysis #Scala #Scala3 #keep
- Explaining the example of linear regression in
-
I have written up a more detailed post about linear regression with #probula using grid approximation. The post focuses on:
- Explaining the example of linear regression in
probula(which is an internal DSL embedded in Scala 3) - Showing how grid approximation is implemented in
probula - Discussing how this implementation is tested and how is it used in testing of other #BayesianInference methods
Enjoy!
https://wasowski.dukla.ch/posts/2606-grid-approximation-with-probula/
#ProbabilisticProgramming #Bayesian #Inference #DataAnalysis #Scala #Scala3 #keep
- Explaining the example of linear regression in
-
I have written up a more detailed post about linear regression with #probula using grid approximation. The post focuses on:
- Explaining the example of linear regression in
probula(which is an internal DSL embedded in Scala 3) - Showing how grid approximation is implemented in
probula - Discussing how this implementation is tested and how is it used in testing of other #BayesianInference methods
Enjoy!
https://wasowski.dukla.ch/posts/2606-grid-approximation-with-probula/
#ProbabilisticProgramming #Bayesian #Inference #DataAnalysis #Scala #Scala3 #keep
- Explaining the example of linear regression in
-
The seventh @scalabridgelondon season starts on the 8th of Oct, and it's gonna be jam packed with interesting Scala related learning activities. Head on to Meetup.com and subscribe!
https://meetu.ps/e/PwvsR/ttMQN/i#scala #scala3 #scalabridge #meetup #functionalprogramming #learning #coding
-
So, after more than 2 years on it, we're almost at the point where #rudder is ported to #scala3 🎉🎉🎉
Rudder is an old beast. 15y old. With lib from that era like (quite fabulous in retrospective) #liftweb by @dpp, XML literals, lib using macro that won't ever be ported to Scala 3, etc.
And Rudder has a very peculiar (self imposed) constraint on branch support, where we need to easily switch to and evolve bra ches 2y old, and upmerge changes.
And still, with the help of some very talented people, it's happening. With regular update to include syntax changes, prepare the code base, check things run in the future version... Without any impact on the release cycle if the product (until now! Still time to bork everything!)
It was an extremely frustrating experience that could have been made easier without the Scala 3.0 big bang but with more iterative small changes like there is in new versions ("the last time syntax will change and books will be written", my ass).
But still, the compat layer allowing to use #scala 2 libs in #scaka3, and the migration tools, are marvels.
-
So, after more than 2 years on it, we're almost at the point where #rudder is ported to #scala3 🎉🎉🎉
Rudder is an old beast. 15y old. With lib from that era like (quite fabulous in retrospective) #liftweb by @dpp, XML literals, lib using macro that won't ever be ported to Scala 3, etc.
And Rudder has a very peculiar (self imposed) constraint on branch support, where we need to easily switch to and evolve bra ches 2y old, and upmerge changes.
And still, with the help of some very talented people, it's happening. With regular update to include syntax changes, prepare the code base, check things run in the future version... Without any impact on the release cycle if the product (until now! Still time to bork everything!)
It was an extremely frustrating experience that could have been made easier without the Scala 3.0 big bang but with more iterative small changes like there is in new versions ("the last time syntax will change and books will be written", my ass).
But still, the compat layer allowing to use #scala 2 libs in #scaka3, and the migration tools, are marvels.
-
So, after more than 2 years on it, we're almost at the point where #rudder is ported to #scala3 🎉🎉🎉
Rudder is an old beast. 15y old. With lib from that era like (quite fabulous in retrospective) #liftweb by @dpp, XML literals, lib using macro that won't ever be ported to Scala 3, etc.
And Rudder has a very peculiar (self imposed) constraint on branch support, where we need to easily switch to and evolve bra ches 2y old, and upmerge changes.
And still, with the help of some very talented people, it's happening. With regular update to include syntax changes, prepare the code base, check things run in the future version... Without any impact on the release cycle if the product (until now! Still time to bork everything!)
It was an extremely frustrating experience that could have been made easier without the Scala 3.0 big bang but with more iterative small changes like there is in new versions ("the last time syntax will change and books will be written", my ass).
But still, the compat layer allowing to use #scala 2 libs in #scaka3, and the migration tools, are marvels.
-
So, after more than 2 years on it, we're almost at the point where #rudder is ported to #scala3 🎉🎉🎉
Rudder is an old beast. 15y old. With lib from that era like (quite fabulous in retrospective) #liftweb by @dpp, XML literals, lib using macro that won't ever be ported to Scala 3, etc.
And Rudder has a very peculiar (self imposed) constraint on branch support, where we need to easily switch to and evolve bra ches 2y old, and upmerge changes.
And still, with the help of some very talented people, it's happening. With regular update to include syntax changes, prepare the code base, check things run in the future version... Without any impact on the release cycle if the product (until now! Still time to bork everything!)
It was an extremely frustrating experience that could have been made easier without the Scala 3.0 big bang but with more iterative small changes like there is in new versions ("the last time syntax will change and books will be written", my ass).
But still, the compat layer allowing to use #scala 2 libs in #scaka3, and the migration tools, are marvels.
-
So, after more than 2 years on it, we're almost at the point where #rudder is ported to #scala3 🎉🎉🎉
Rudder is an old beast. 15y old. With lib from that era like (quite fabulous in retrospective) #liftweb by @dpp, XML literals, lib using macro that won't ever be ported to Scala 3, etc.
And Rudder has a very peculiar (self imposed) constraint on branch support, where we need to easily switch to and evolve bra ches 2y old, and upmerge changes.
And still, with the help of some very talented people, it's happening. With regular update to include syntax changes, prepare the code base, check things run in the future version... Without any impact on the release cycle if the product (until now! Still time to bork everything!)
It was an extremely frustrating experience that could have been made easier without the Scala 3.0 big bang but with more iterative small changes like there is in new versions ("the last time syntax will change and books will be written", my ass).
But still, the compat layer allowing to use #scala 2 libs in #scaka3, and the migration tools, are marvels.
-
#Scala it's that (and there's a lot of them), and also more. I think scala pushed the state of art regarding effect system, and things like #catseffect (more "Haskell inspired") and #zio (more "a Scala own thing") are quite amazing.
And #scala3 has really impressive things regarding types (see for ex #iron https://social.treehouse.systems/@fanf42/111935214728958950) -
#Scala it's that (and there's a lot of them), and also more. I think scala pushed the state of art regarding effect system, and things like #catseffect (more "Haskell inspired") and #zio (more "a Scala own thing") are quite amazing.
And #scala3 has really impressive things regarding types (see for ex #iron https://social.treehouse.systems/@fanf42/111935214728958950) -
"We’re happy to announce the release of Scala Native. Scala Native 0.4.16 is yet another maintenance release backporting changed from the 0.5.0-SNAPSHOT branch. This version introduces support for using Scala Native with JDK 21 and introduces bug fixes to the runtime. It also fixes severe performance problems when using java.nio.MappedByteBuffers."
https://scala-native.org/en/stable/changelog/0.4.16.html
#scala #scala3 #ScalaNative #programming #fp #programmingLanguages
-
"We’re happy to announce the release of Scala Native. Scala Native 0.4.16 is yet another maintenance release backporting changed from the 0.5.0-SNAPSHOT branch. This version introduces support for using Scala Native with JDK 21 and introduces bug fixes to the runtime. It also fixes severe performance problems when using java.nio.MappedByteBuffers."
https://scala-native.org/en/stable/changelog/0.4.16.html
#scala #scala3 #ScalaNative #programming #fp #programmingLanguages
-
"We’re happy to announce the release of Scala Native. Scala Native 0.4.16 is yet another maintenance release backporting changed from the 0.5.0-SNAPSHOT branch. This version introduces support for using Scala Native with JDK 21 and introduces bug fixes to the runtime. It also fixes severe performance problems when using java.nio.MappedByteBuffers."
https://scala-native.org/en/stable/changelog/0.4.16.html
#scala #scala3 #ScalaNative #programming #fp #programmingLanguages
-
"We’re happy to announce the release of Scala Native. Scala Native 0.4.16 is yet another maintenance release backporting changed from the 0.5.0-SNAPSHOT branch. This version introduces support for using Scala Native with JDK 21 and introduces bug fixes to the runtime. It also fixes severe performance problems when using java.nio.MappedByteBuffers."
https://scala-native.org/en/stable/changelog/0.4.16.html
#scala #scala3 #ScalaNative #programming #fp #programmingLanguages
-
"We’re happy to announce the release of Scala Native. Scala Native 0.4.16 is yet another maintenance release backporting changed from the 0.5.0-SNAPSHOT branch. This version introduces support for using Scala Native with JDK 21 and introduces bug fixes to the runtime. It also fixes severe performance problems when using java.nio.MappedByteBuffers."
https://scala-native.org/en/stable/changelog/0.4.16.html
#scala #scala3 #ScalaNative #programming #fp #programmingLanguages
-
New blog post! Let's continue to write a parser combinator library in Scala 3 à la @pchiusano and @runarorama 's Red book... but using TDD!
#scala3 #tdd #parsercombinatorshttps://blog.agilogy.com/2022-12-16-writing-a-parser-combinator-library-2.html