News for hackers. Stuff that matters.
Re:Push ifs up and fors down by ryanjshaw on Wednesday November 15, 2023 @05:41PM (#38283628)
I wrote some batch (list) oriented code for a static analyzer recently.

It was great until I decided to change my AST representation from a tuple to a generic type with a corresponding interface i.e. the interface handled the first member of the tuple (graph data) and the generic type the second member (node data).

This solved a bunch of problems but all list-oriented code broke because the functions operating on a list of generics types couldn't play nice with the functions operating on lists of interfaces.

I ended up going back to scalar functions pipelined between list functions.

Re:Push ifs up and fors down by aeonik on Wednesday November 15, 2023 @07:02PM (#38284162)
I'm curious, why couldn't the list of generic types play nice with functions operating on lists of interfaces?
Re:Push ifs up and fors down by ryanjshaw on Thursday November 16, 2023 @12:19AM (#38286024)
Have a look here: https://onecompiler.com/fsharp/3ztmx2uhr

Basically we want a "Yes" or a "No" when the family has children:

    let kidsYN = family |> numberOfChildren |> yesOrNo
But we get:

    error FS0001: Type mismatch. Expecting a
      INode list    
    but given a
      Node<Person> list    
    The type 'INode' does not match the type 'Node<Person>'
Forcing us to do:

    let familyAsINode = family |> List.map (fun n -> n :> INode)
Sure you can wrap this up in a function but it's ugly and annoying to have to use this everywhere and takes away from your logic. It ends up being better to split your "batch" and "scalar" operations and compose them e.g. by introducing a "mapsum" function:

    let kidsYN2 = family |> mapsum numberOfChildrenV2 |> yesOrNo