Here is a fast explanation on this study for Freek to improve compile-time:
https://github.com/ProjectSeptemberInc/freek/blob/optim/cop/src/main/scala/CoproductK.scala#L14-L34
In Freek, Higher-Kinded Coproduct was based on Shapeless HList/Coproduct representation like:
sealed trait CoproductK[A] extends Product with Serializable
sealed trait CNilK[A] extends CoproductK[A]
Copyright © 2016-2018 Fantasyland Institute of Learning. All rights reserved.
A function is a mapping from one set, called a domain, to another set, called the codomain. A function associates every element in the domain with exactly one element in the codomain. In Scala, both domain and codomain are types.
val square : Int => Int = x => x * x
This is my attempt to give Scala newcomers a quick-and-easy rundown to the prerequisite steps they need to a) try Scala, and b) get a standard project up and running on their machine. I'm not going to talk about the language at all; there are plenty of better resources a google search away. This is just focused on the prerequisite tooling and machine setup. I will not be assuming you have any background in JVM languages. So if you're coming from Python, Ruby, JavaScript, Haskell, or anywhere… I hope to present the information you need without assuming anything.
Disclaimer It has been over a decade since I was new to Scala, and when I was new to Scala, I was coming from a Java and Ruby background. This has probably caused me to unknowingly make some assumptions. Please feel free to call me out in comments/tweets!
One assumption I'm knowingly making is that you're on a Unix-like platform. Sorry, Windows users.
| #!/usr/bin/env stack | |
| -- stack --resolver lts-9.5 script --package scotty | |
| {-# LANGUAGE OverloadedStrings #-} | |
| import Web.Scotty | |
| import Data.Monoid (mconcat) | |
| main = scotty 3000 $ do |
Please see this response for more context.
Dear Mr. Brown:
We represent the legal interests of our client, Mr. John Arlen De Goes, Maryland, USA.
For several years now, you have repeatedly defamed our client on the internet. Your public blog https://meta.plasm.us/posts/2019/09/01/jdg-and-the-fp-community/ specifically targets our client with the goal to publicly vilify our client. This blog can be easily found with the help of search engines like Google by just searching for the name of our client. On this blog, amongst other false statements, you falsely allege the following about our client:
Think of all the arguments you've heard as to why static typing is desirable — every single one of those arguments applies equally well to using types to represent error conditions.
An odd thing I’ve observed about the Scala community is how many of its members believe that a) a language with a sophisticated static type system is very valuable; and b) that using types for error handling is basically a waste of time. If static types are useful—and if you like Scala, presumably you think they are—then using them to represent error conditions is also useful.
Here's a little secret of functional programming: errors aren't some special thing that operate under a different set of rules to everything else. Yes, there are a set of common patterns we group under the loose heading "error handling", but fundamentally we're just dealing with more values. Values that can have types associated with them. There's absolutely no reason why the benefits of static ty
| local configs = require 'lspconfig.configs' | |
| local lspconfig = require 'lspconfig' | |
| -- Check if the config is already defined (useful when reloading this file) | |
| if not configs.ensime then | |
| configs.ensime = { | |
| default_config = { | |
| cmd = { | |
| 'java', '-jar', os.getenv("HOME") .. '/.cache/ensime/lib/ensime-lsp.jar' | |
| }, |