Monday, March 1, 2021

March 2021 1HaskellADay Problems and Solutions

Monday, February 1, 2021

February 2021 1HaskellADay Problems and Solutions

Thursday, January 21, 2021

January 2021 1HaskellADay 1Liners

  • 2021-01-28: Opposite problem:
    You have: [(a, Set b)]
    you want: [(a, b)]
    e.g.:  [("hi", fromList [1,2,3]), ("bye", fromList [4,6,7]) ->
    [("hi",1),("hi",2),("hi",3),("bye",4),("bye",6),("bye",7)]
    Interestingly, Set is not a Monad. wut. How do you get around that problem?
    • D Oisín Kidney @oisdk (>>= traverse toList)
    • mine: concatMap (sequence . second Set.toList)
  • 2021-01-28: 
    We have [(Set a, b)]
    we want [(a, b)] 
    where each element of Set a is paired with b, e.g.:
    [(fromList [1,2,3], 'a'), (fromList [4,5,6], 'b')]
    becomes
    [(1,'a'),(2,'a'),(3,'a'),(4,'b'),(5,'b'),(6,'b')]
    • Steve "wash your hands" Trout @strout:
      concatMap (uncurry (liftA2 (,)) . bimap toList pure)
    • insatiable mask wearer @tim_1729
      [(a,b) | (s,b) <- xs, a <- (toList s)]
  • Today, 2021/01/21, is:
    1. Can be written with only 3 digits, What other dates can be so written? Also:
    2. a day where the month and day are NOT amalgamation the year. But which dates are amalgamations?

Wednesday, January 20, 2021

January 2021 1HaskellADay Problems and Solutions

Tuesday, December 1, 2020

December 2020 1HaskellADay Problems and Solutions

Friday, November 13, 2020

November 2020 1HaskellADay 1Liner problems and solutions

  •  In my Data.XHTML library

    printXML xml = (\elt -> printElementWithOffset elt 0 >> return elt) (rep xml)

    Curry away the xml-argument to the printXML-function 

Tuesday, November 3, 2020

November 2020 Haskell Problems and Solutions

  • 2020-11-27: Is the morse code table generated from a graph better than by-hand? In today's #haskell problem, WE FIND OUT! 😤  Today's #haskell solution shows I did code the morse table by hand correctly! *whew* and also show how to extract data from a graph-store. And! has Konami's super-secret cheat-code! ^^vv<><>ba (shh! Don't tell anyone!) 

  • 2020-11-25: 'Lorem Ipsum' never looked so good ... IN MORSE CODE! :< Today's #haskell problem. Today's #haskell solution shows that Cicero had words. Yes, he did.  


  • 2020-11-23: Today's #haskell problem: ALLIANCES o' the WORLD! UNITE! (like Wonder Twin powers). As today IS Tuesday, it IS Belgium! Displaying the countries of NATO. 

  • 2020-11-20: If today WERE Tuesday, it would be ... Belgium. Today is Friday, however. (whispered: but it's still Belgium). Today's #haskell problem: render a country's air-power as KML to display on earth.google.com, or some such-like.  Today is Friday, so this must be ... Bruxelles! ... I'll allow it. Today's #Haskell solution maps Brussels and all the air bases of Belgium. 


  • 2020-11-18: As yesterday's problem of enhancing countries with additional information was SO EASY 🙄 for today's #haskell we'll take what we learned yesterday and enhance our stored continents with wikidata.org information. I'll let the band Toto explain today's #Haskell solution. "I BLESSED THE QID IN AAAAAAFRICA!" 🎵🎶 Thanks, fellahs. 🙄😎  

  • 2020-11-17: We find out capitals of ... um: 'thingies' (?) from wikidata.org for today's #haskell problem. Belgium has a wikidata.org q-id; captured in our knowledge graph. Belgium has a capital, too: Brussels, along with a lat/long coordinate; also captured. Today's #haskell solution was to map all q-id's and capitals to countries of the world

  • 2020-11-13: Today's #haskell problem? We convert our alliances and airbases graph into XML (specifically, KML). Why? you ask? BECAUSE WE CAN! ... and to get ready for ... this: #geodesicmapping Today's #haskell solution is our first two folders in KML. I'M SO PROUD OF YOU! ... hey! I can see my house from here!  
     


  • 2020-11-12: How big is our unicode-... dare I call it a 'problem'? It's not a 'problem,' but it's stopping us from talking with the REST endpoint successfully. So, today's #haskell problem is: how many non-ASCII unicode points do we have in our Alliances? You want alliances-as-a-graph? You got alliances-as-a-graph!  

  • 2020-11-11: For today's #haskell problem we attempt to upload our alliances to our Continent/Country/Airbase graph. HOW WILL THIS ATTEMPT TURN't OUT? The suspense. It's killing me. IT TURN't OUT BAD! IT TURN't OUT BAD! Bad unicode! Bad! le sigh. Today's #haskell solution (which was for yesterday's problem) leads to tomorrow's (today's, actually) Haskell problem. So it goes. 
  • 2020-11-10: The BIG KAHUNA: the military alliances of the world, derived from both wikidata and wikitext. Bringing it all together with the Organization of American States is today's #haskell problem. #BigKahuna Today's #haskell solution: and here we ... [wait for it] ... go
  • 2020-11-09: In today's #haskell exercise, we add the United Nations to the AllianceMap. Today's #haskell solution adds the United Nations to the map of world military alliances. 
  • 2020-11-06: For today's #haskell problem we add the European Union to the list of military alliances. Today's #haskell solution: European Union from wikidata.org JSON, GET! 
  • 2020-11-05: Today's #haskell problem: rolling in missing alliances and aliases (and implementing alias-parsing). 42. That's the number of alliances today's #haskell solution collected from wikitext. Coincidence? I THINK NOT! #DeepThought 
  • 2020-11-04: "We have work to do!" el geophf declares. And so, the #haskell work: missing alliancesThe good news is that there's bad news: today's #haskell solution shows that we've missed 35 alliances in our parsing. 
  • 2020-11-03: Today's #haskell problem: I give you a new, funky parser for new, funky alliances! ... and who was it who said that Haskell is no fun? We refine our parsed results, by hand-parsing missed results for today's #haskell solution.