Yannick Loiseau
Yannick Loiseau
I don't know if you have considered [dateutil](https://dateutil.readthedocs.org/en/latest/) but I find it useful for fuzzy human date parsing. Example from the doc: ``` python >>> from dateutil.parser import parse >>>...
I don't get your first point... (see http://golo-lang.org/documentation/next/golodoc/gololang/Functions.html)
I'm not sure that it's relevant to dedicate a guide (sub)section for each and every standard module. I view the guide as a documentation on the language itself, along with...
ping @jponge @franckverrot @danielpetisme
@franckverrot even with autocurry, if your signature changes, say you add a final parameter, you'll need to change the calls anyway, or you'll end up with partialized functions everywhere :smile:
@franckverrot I agree. I'm also more inclined to the autocurry solution. But I was answering your remark that you need to add placeholders if signature changes. The fact is that...
Moreover, the placeholder approach could be compile time syntactic sugar… Note that the solutions are not mutually exclusives :smile:
Hum... no it could not be compile time syntactic sugar :disappointed: We must do the same lookup as for functions, and thus `foo("a", ?)` can't be replaced by `^foo: bindTo("a")`...
Regarding methods, it would be nice if, given an object with a `:foo(x, y)` method ``` golo let f = o: foo(?, "a") ``` would be equivalent to ``` golo...
As a POC, I just hacked a macro that implements the placeholder approach, but with a `$` since it must be a valid Golo identifier (it could have been `_`)...