Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Jul 04 15:13
    hannesm commented #939
  • Jun 30 09:40
    raphael-proust commented #923
  • Jun 30 09:39
    raphael-proust opened #959
  • Jun 29 16:37

    ilankri on prepare-for-5.6.1-release

    (compare)

  • Jun 29 16:29

    ilankri on prepare-for-5.6.1-release

    (compare)

  • Jun 29 13:12
    raphael-proust commented #956
  • Jun 29 13:03
    mroch commented #956
  • Jun 29 12:58
    raphael-proust commented #956
  • Jun 29 12:57

    raphael-proust on master

    Set version in CHANGES Set version in opam file Merge pull request #958 from oc… (compare)

  • Jun 29 12:57
    raphael-proust closed #958
  • Jun 29 06:53
    raphael-proust commented #958
  • Jun 29 06:51
    raphael-proust opened #958
  • Jun 29 06:49

    raphael-proust on 5.6.1

    (compare)

  • Jun 29 06:49

    raphael-proust on prepare-for-5.6.1-release

    Set version in CHANGES Set version in opam file (compare)

  • Jun 28 15:28
    raphael-proust closed #957
  • Jun 28 15:28

    raphael-proust on master

    Improve Lwt_process tests - do… Change wrong O_CLOEXEC to O_KEE… Simplify Unix cloexec for passi… and 2 more (compare)

  • Jun 28 15:24
    raphael-proust commented #957
  • Jun 28 10:05
    MisterDA synchronize #957
  • Jun 28 08:09
    MisterDA commented #957
  • Jun 28 08:09
    MisterDA synchronize #957
matrixbot
@matrixbot
Orbifx scattered for now. Search for #ocaml to follow other ocamlers
Anton Bachin
@aantron
@theindigamer i rewrote the introduction, updated the tutorial, added an execution model section, and properly wrote the guide to rest of lwt in the new manual draft. rendered it to html, take a look here https://ocsigen.github.io/lwt/manual-draft/Lwt.html
would be interested to see if this is helpful, and in any other feedback you may have :)
Varun Gandhi
@theindigamer
@aantron the first couple of sections look good to me :smile:. I'll probably go through the rest over the weekend and get back to you then.
matrixbot
@matrixbot
Orbifx Any bloggers here? Want an opinion on something
Anton Bachin
@aantron
not me. im just a wannabe :p
Varun Gandhi
@theindigamer

I finished reading the sections before Sec. Rejection. Comments:

  1. Links to lwt functions are dead.
  2. In Sec. Execution Model, the word "resolution" is used as a noun but it isn't mentioned before. Do you intend to use I/O promise instead?
  3. In Sec. Waiting, should

    If p1 is fulfilled now or later with value v, f v is called. f v might be called immediately, or after some time.

    instead have something like "f v will be called when p1 is fulfilled"?

  4. "Actual promises are read-only.", it's not fully clear what that means ... it can't mean that promises are immutable (because you can resolve them through the resolver). Are they read-only modulo resolvers (which are typically hidden away and not used directly)? It might be better to have a few more words here :smile:.

Apart from these, I think the rest of it is a good read.

Also, for some reason, the deprecated section is not linked to in the sidebar.

Romain Slootmaekers
@toolslive
We tried to move our dependency from lwt.3.0.0 to lwt.3.1.0, but we noticed some of our tls related testcases started failing. Before I start digging: Did anybody else witness problem with tls and lwt3.1.0 as well ?
Anton Bachin
@aantron
@toolslive: i'm not aware of any reports, or any other problems with lwt 3.1.0, at this point
@theindigamer: thanks. the links to anything outside this module are dead, because it's just one file uploaded for now. i suppose i should put the rest of the current manual in the same directory. also, ive since rewritten most of the function docs. i'll incorporate your feedback :) i hid the deprecated section on purpose, but ive since also put it back, without linking its subsections in the sidebar
basically, as suggested, only the intro parts of that were ready for consumption :)
Anton Bachin
@aantron
the new module Lwt docs are now a PR ocsigen/lwt#469
matrixbot
@matrixbot
Orbifx Anton Bachin (Gitter): is this how Lwt implements Lwt exceptions? https://hal.inria.fr/inria-00432575/document
Anton Bachin
@aantron
Orbifx: sort of. the "basic" Lwt is an I/O monad combine with an error monad (something we might later undo)
(and separate the monads)
this basic error monad carries around exn for errors, an open variant type
there is also Lwt_result, which provides a separate error monad
with it, the user can choose what types to use for carrying around errors. they could be string, or some inferred polymorphic variant, or an open variant, or anything else
matrixbot
@matrixbot
Orbifx I know, I use result :)
Anton Bachin
@aantron
cool :)
yeah, just being thorough :)
Anton Bachin
@aantron
Lwt 3.2.0 is now fully out
Pavel Argentov
@argent-smith
good job ))) you forced me to learn up the Logs )))
Anton Bachin
@aantron
hope its real :) btw you can still use Lwt_log for a long time, it won't be broken.. but if it ever is, it will get a constraint on which version of Lwt it can work with
Pavel Argentov
@argent-smith
With Logs my tests work better ))
Actually, I've learned them both. Lwt_log is easier to start with; Logs is better to elaborate on )
matrixbot
@matrixbot
Orbifx Why has this room got lobby in the name?
Anton Bachin
@aantron
@argent-smith great :)
Orbifx: i don't know, it's the default room created by gitter
Romain Slootmaekers
@toolslive
Did anyone compare performance of Lwt.2.7.0, Lwt.3.0.0, ....Lwt.3.2.1 (or a subset of these) ? Since I observed no bad performance related news, can I assume it's at least qualitatively 'similar' ?
Anton Bachin
@aantron
@toolslive it should be basically unchanged
two of the plots in this graph effectively compare performance of lwt 3.1.0 to 3.2.0 https://github.com/ocsigen/lwt/pull/500#issuecomment-343535322
it looks unchanged
in my own measurements while making changes, the effects were something like small-percentage slowdowns of bind. given that bind is by far not the most common or time-intensive operation performed in an lwt program, i also expected there to be no real effect
Pavel Argentov
@argent-smith
@aantron are there any breaking changes/regressions between 2.7.0 and 3.2.0? (except all those deprecations we know about)
Anton Bachin
@aantron
@argent-smith i believe all the breaking changes are the ones listed in the changelog here https://github.com/ocsigen/lwt/releases/tag/3.0.0, also you can see details here ocsigen/lwt#308
if anything else broke, it's an accident, and we are not aware of any such accidents
matrixbot
@matrixbot
Orbifx Is there a mailing list for oscsigen or lwt?
Orbifx Ocsigen*
Anton Bachin
@aantron
i am vaguely aware of a mailing list for ocsigen, but not one that i use. perhaps @Drup can say better than i
matrixbot
@matrixbot
smondet Orbifx: http://ocsigen.org/ → “Support & community”
Mailing list and #ocsigen
smondet both are low traffic, but stuff still happens
matrixbot
@matrixbot
Orbifx Nice. Would have eventually checked
Anton Bachin
@aantron
smondet: thanks
Anton Bachin
@aantron
Orbifx: i understand the preference for LGPL. would you still allow your contribution to be relicensed under MIT?
matrixbot
@matrixbot
Orbifx I guess, the vast majority of contributors went for that. But I do wonder if they would have been similarly positive for a copyleft licence.
Orbifx Anton Bachin (Gitter): is there a particular reason for choosing MIT? something tactical?
matrixbot
@matrixbot
smondet Orbifx: my 2c: In Ocaml since linking is static, it cannot really be LGPL, it kinda has to be LGPL+Linking-exn. which is a hack that maybe some INRIA lawyer checked in like 1994, but that adds a ton weirdness to an already pretty crazy license (have you tried to read the LGPL itself?).
Orbifx smondet: I have read some of it and about it in the past. ALso, forgot that OCaml does static linking so I can see the issue