Hello, that doesnâ(TM)t seem right.
[code]
qsort (x:xs) = qsort (filter (=x) xs)
qsort [] = []
[/code]
This performs better:
[code]
qsort (x:xs) = qsort ls ++ [x] ++ qsort rs
where
(ls,rs) = foldl f ([],[]) xs
f (ls',rs') (x':xs')
| x' x = ((x':ls'),rs')
| otherwise = (ls',(x':rs'))
[/code]
Excuses if the code does not compile or run. I am on a mobile device and havenâ(TM)t attempted to compile it.
I am a Haskell programmer, and I have used Haskell pretty much for everything during the last three years. I do not know only Haskell. I know Perl, JavaScript, Python, Java, C, C++ and Scala fluently, as well as an assortment of smaller and special-purpose languages like PHP and Bash. It cannot be said of me that I only know how to use a hammer. Quite the contrary, it was frustration with the high error rate of my programs, along with some best practices I started to develop on my own, unaware of functional programming, which led me down the Haskell road.
I find that your description of the Haskell ethos is accurate. We like correct solutions for problems, and we know that many of these solutions do not yet exist, so instead of hacking something together, we tend to prefer to explore the problem space logically until a mathematically sound solution can be found. That solution will map to Haskell painlessly, once found.
Saying someone deserves to die and killing them is not the same thing. Preventing further crime by locking up dangerous individuals without punishing them is what I expect from a civilized society. Institutionalized killing of people to exert punitive vengeance is incredibly cruel and it is only done by savages.
Slashdot Mirror
Hello, that doesnâ(TM)t seem right. [code] qsort (x:xs) = qsort (filter (=x) xs) qsort [] = [] [/code] This performs better: [code] qsort (x:xs) = qsort ls ++ [x] ++ qsort rs where (ls,rs) = foldl f ([],[]) xs f (ls',rs') (x':xs') | x' x = ((x':ls'),rs') | otherwise = (ls',(x':rs')) [/code] Excuses if the code does not compile or run. I am on a mobile device and havenâ(TM)t attempted to compile it.
I am a Haskell programmer, and I have used Haskell pretty much for everything during the last three years. I do not know only Haskell. I know Perl, JavaScript, Python, Java, C, C++ and Scala fluently, as well as an assortment of smaller and special-purpose languages like PHP and Bash. It cannot be said of me that I only know how to use a hammer. Quite the contrary, it was frustration with the high error rate of my programs, along with some best practices I started to develop on my own, unaware of functional programming, which led me down the Haskell road. I find that your description of the Haskell ethos is accurate. We like correct solutions for problems, and we know that many of these solutions do not yet exist, so instead of hacking something together, we tend to prefer to explore the problem space logically until a mathematically sound solution can be found. That solution will map to Haskell painlessly, once found.
Of all keyboards I had, this is the one I have liked most. There is also the K811 for Mac.
Saying someone deserves to die and killing them is not the same thing. Preventing further crime by locking up dangerous individuals without punishing them is what I expect from a civilized society. Institutionalized killing of people to exert punitive vengeance is incredibly cruel and it is only done by savages.