<xvilka>
how you even write Anstrom parsers without documentation?
<xvilka>
totally unintuitive
<xvilka>
I am trying to write a simple parser for a superset of CSV, and spent half a day already, trying to figure how to do that with Angstrom, with no luck yet
<Drup>
xvilka: you haven't used any parser generator library before, I presume ?
<Drup>
parser combinator library*
<xvilka>
Drup: used menhir
<xvilka>
I just decided to try Angstrom, because it claims to be monadic and faster
Serpent7776 has joined #ocaml
<Armael>
faster... than other parser combinators
<xvilka>
also errors are nondescriptive
<Drup>
unless you want streaming/operate inside a monad, or something that is much richer than LR, you're better of with menhir
<dmbaturin>
I need to try menhir's new error reporting features.
<xvilka>
Drup: thx for the hint
mfp has joined #ocaml
<xvilka>
anyway, already figured the problem, as always my own fault - I wasn't checking for EOL when combining multiple rules, e.g. you need (rule1 <* eol) <$> (rule2 <* eol), etc
<Drup>
if we generalized everything, we would generalize x to 'a option ref, which is unsound
<octachron>
Well, yes. I am not sure I see the difference with my example?
<Drup>
It's more straighforward ? :D
<Drup>
It also explains the reason for the "set once" nature of week variables
<octachron>
Ah sure, it is the problem with trying to mesh up together the eta-expansion and weak variable explanation in a short post.
<Drup>
well, the eta expansion is kinda artificial anyway....
<Drup>
(the compiler could do it for us)
iovec has joined #ocaml
<octachron>
Does that not risk to mix typechecking and semantics? For instance, a side-effect would be executed only if the return type is generalisable.
andreas303 has quit [Remote host closed the connection]
<Drup>
you need to be careful, yeah
andreas303 has joined #ocaml
andreas303 has quit [Remote host closed the connection]
andreas303 has joined #ocaml
themsay has quit [Ping timeout: 245 seconds]
FreeBirdLjj has joined #ocaml
FreeBirdLjj has quit [Ping timeout: 244 seconds]
themsay has joined #ocaml
spew has joined #ocaml
FreeBirdLjj has joined #ocaml
AtumT has joined #ocaml
ygrek has joined #ocaml
Haudegen has quit [Remote host closed the connection]
sagax has quit [Ping timeout: 245 seconds]
iAmerika1 has joined #ocaml
uzuki has joined #ocaml
barockobamo has quit [Remote host closed the connection]
robmyers_ has joined #ocaml
chindy_ has joined #ocaml
erwanou_ has joined #ocaml
logicmoo has joined #ocaml
krkini has joined #ocaml
robmyers has quit [*.net *.split]
kini has quit [*.net *.split]
tg has quit [*.net *.split]
dmiles has quit [*.net *.split]
chindy has quit [*.net *.split]
erwanou has quit [*.net *.split]
robmyers_ is now known as robmyers
logicmoo is now known as dmiles
tg has joined #ocaml
sveit has quit [Ping timeout: 248 seconds]
jao has quit [Remote host closed the connection]
jao has joined #ocaml
sveit has joined #ocaml
dhil has quit [Ping timeout: 245 seconds]
freyr69 has quit [Remote host closed the connection]
q9929t has joined #ocaml
FreeBirdLjj has quit [Remote host closed the connection]
iovec has quit [Quit: Connection closed for inactivity]
jao has quit [Remote host closed the connection]
jao has joined #ocaml
ziyourenxiang has quit [Ping timeout: 245 seconds]
q9929t has quit [Quit: q9929t]
dhil has joined #ocaml
Haudegen has joined #ocaml
<Haudegen>
The latest vim updates in Debian break my development setup (filetype information gets lost when changing buffer). Does anybody have a solution for this?
<oni-on-ion>
emacs here
<Haudegen>
oni-on-ion: So you want me to switch? :)
<oni-on-ion>
Haudegen, nah, just wanted to show that someone is here, altho i cant help =)
<oni-on-ion>
but using emacs eyes, i'd say thats a fairly undesirable behavior, i'd check vim scripts that were changed. there might be a way to 'diff' from previous vim install
<oni-on-ion>
yeh. ive never done much vim but spacemacs does look nice visually
<Haudegen>
oni-on-ion: The vim update contains changes in the "source" command, which reads configuration files. The problem disappears after downgrading vim. So I'm fairly sure it's the vim update.
<oni-on-ion>
Haudegen, makes sense. i wonder if the configs need updating as well ?
<oni-on-ion>
i am not sure the details. i wonder if there is a #vim ? or if it is specifically the ocaml configs for vim?
<oni-on-ion>
myself i am using an older version of ocaml support on emacs because the newer one removes operator highlighting which i really want and need
<Haudegen>
oni-on-ion: Maybe. "source" is such a basic command, it'll be quite difficult to find the source of the problem.
<oni-on-ion>
hmm cant trace or step through it ?
<Haudegen>
oni-on-ion: I don't have problems with my setup for other languages (SQL, Shell, Python, ...). There is no ticket in the merlin bug tracker. Hmmm...
<oni-on-ion>
i guess here is where i can say something about emacs. (and not just that its expected behavior rarely changes from under you)
<Haudegen>
oni-on-ion: Everything works fine until I split the screen and change one of the buffers. The "old" buffer loses it's "filetype". I'm not sure how to debug this. Maybe someone here has already solved the problem.
<oni-on-ion>
(for emacs one can run debugger as the configs is full lisp code and emacs itself is the fancy compiler/ide for it.) but i'd rather you get back to ocaml coding ^_^
<oni-on-ion>
haven't heard or seen much activity for ocaml and vim. i would suggest poking into #vim channel and see if there is a simple fix
<Haudegen>
oni-on-ion: Emacs has it's advantages for sure. But my good old Debian stable usually doesn't betray me like this. Hmmm...
<oni-on-ion>
(along with an understanding of why it broke in the first place)
<oni-on-ion>
hehe. im on debian testing, i still compile emacs straight from git because the packaged one is not recent enough
<Haudegen>
I've a Buster machine, no problems there. :) But it's a simpler setup. Maybe Buster hasn't got the update yet. Testing branch works differently.
<oni-on-ion>
i see
<Haudegen>
oni-on-ion: OK, I've started harassing the Vim and Debian guys. Thanks for your support.
<oni-on-ion>
awesome. i hope it works out !
<Haudegen>
oni-on-ion: And there is always the possibility to switch over to the church of Emacs. I've attended another Stallman speech last week, it was great. :)
<oni-on-ion>
was it ? i havent heard/seen any. but several quotes i dont know much about the guy, though i've been neck deep in foss and emacs forever
<Haudegen>
oni-on-ion: He has very strong opinions, but he presents them in a very entertaining way. You'll start saying "GNU/Linux" (instead of "Linux") and "free software" (instead of "open source") for sure.
<companion_cube>
his war on vim is a bit tiresome, though
<oni-on-ion>
Haudegen, i can agree with those =)
<Haudegen>
companion_cube: He has no objection to Vim, as long you use a version with a "free" license.
<oni-on-ion>
(unless referring to kernel or non-free open source, ofc)
<companion_cube>
well his jokes about "vi vi vi", but whatever
<Haudegen>
oni-on-ion: Of course! :)
<Haudegen>
companion_cube: He was asked about Vim at his speech last week, he was very forgiving. Maybe he's getting old and soft (but I don't think so).
Haudegen has quit [Read error: Connection reset by peer]
Haudegen has joined #ocaml
dhil has quit [Ping timeout: 246 seconds]
Jesin has quit [Quit: Leaving]
Jesin has joined #ocaml
themsay has quit [Read error: Connection reset by peer]
Haudegen has quit [Read error: Connection reset by peer]
<[rg]>
thank you
<Leonidas>
I had to login to yahoo and yahoo promptly sent me an email about an unexpected login. They are absolutely right, it is 2019 and I log in to yahoo? Who in the world would do that :D
<[rg]>
lol
<[rg]>
I may have asked before but which pathway?
<[rg]>
janestreet has their opensource libs as well
<Leonidas>
pathway?
<[rg]>
in learning ocaml
<[rg]>
i.e books, since some use different libs
<Leonidas>
Personally I can only really recommend RWO. The others I found rather meh.
<[rg]>
ok, thanks :)
<Leonidas>
(And yes, RWO uses somewhat idiosyncratically Core, but having used both the stdlib and core/base I vastly prefer the latter)