`munge` and `compute` seem identical in functionality

[mahmoudimus]

Why are they two semantically different things?

[bninja]

they are 2 diff things, outline of mapping steps here: https://github.com/bninja/pilo/blob/master/pilo/fields.py#L214-219

compute by default resolves data from a src and parses it. you'll hook that if its computed in a diff way e.g. derived off of other fields.

munge typically does xforms on whatever was computed (e.g. lowcase, apply translation map, etc).

so u'd hook compute if you are altering how its base-line computed and munge if you just want to fiddle with what was computed.

but if easy to call default impl from hook then munge is probably not neccessary, e.g.

class Form(pilo.Form):

    f = pilo.fields.String()

    @f.compute
    def f(self)
        return f.compute().lower()