Tweetovi

Blokirali ste korisnika/cu @bobzhang1988

Jeste li sigurni da želite vidjeti te tweetove? Time nećete deblokirati korisnika/cu @bobzhang1988

  1. prije 7 sati
    Poništi
  2. 3. velj

    You can do one-liner in Bucklescript too, here is an example: ``` install$npx bsc -e 'Js.log (.([|1,2,3,3,4,2|]->fromArray->toArray))' | node - [ 1, 2, 3, 4 ] ```

    Poništi
  3. 18. sij

    we also support json with comments, so you can config vscode as jsonc mode as below: ``` "files.associations": { "bsconfig.json" : "jsonc" } ```

    Prikaži ovu nit
    Poništi
  4. 18. sij

    A less known but quite useful feature: we support schema validation for bsconfig.json which is well integrated with vscode, see my pic for example in the vscode configuration, it gives you json validation, auto completion for free.

    Prikaži ovu nit
    Poništi
  5. proslijedio/la je Tweet
    15. sij
    Odgovor korisnicima i sljedećem broju korisnika:

    Ppl are shipping Go & Node apps like no tomorrow, but Haskell apps few and far between. We need to think about OCaml's relative strengths and its positioning–imho it has the potential to move towards the 'Go/Node-like' niche in perception–because it already has their abilities.

    Poništi
  6. 15. sij

    We compile OCaml record to object since version 7 which is really nice, but sometimes you would like to compile record to array for various reasons this is possible due to inline records, see this diff for example

    Poništi
  7. 14. sij

    In next release, we will reuse part of the so that we understand better of `raw` in which means even better js interop. (Both projects are written in )

    Poništi
  8. 10. sij

    this is essential since your lib no longer depends on a particular compiler, much easier to build

    Prikaži ovu nit
    Poništi
  9. 10. sij

    If you depend a particular ppx, you can get rid of such dependencies for your end users, here is an example: ``` bsc -dsource -bs-syntax-only -ppx '`ocamlfind query sedlex`/ppx/ppx.exe --as-ppx' -impl flow_lexer_sedlex.ml &>flow_lexer.ml ```

    Prikaži ovu nit
    Poništi
  10. 10. sij

    Still remember sedlex used to have no dependency (only one dev), now it depends on the whole universe...

    Prikaži ovu nit
    Poništi
  11. 10. sij

    Spending a whole day dealing with dependencies when evaluating a third party lib: less is more, life is short, don't drag in dependencies unless you have to!

    Prikaži ovu nit
    Poništi
  12. 1. sij

    Happy New Year@2020 !

    Poništi
  13. proslijedio/la je Tweet
    30. pro 2019.

    Reflecting these days about HOW MUCH happened this year in the ReasonML/OCaml community. These are some highlights, def missing many events and releases (especially on the OCaml side, as I follow closer Reason & BuckleScript), but feel free to add below in comments. Let's go! 🚀

    Prikaži ovu nit
    Poništi
  14. 29. pro 2019.

    There is also Sys.backend_type for platform dependent program

    Tweet je nedostupan.
    Poništi
  15. 22. pro 2019.

    Note it does not need to be compiled since it is just surface syntax

    Prikaži ovu nit
    Poništi
  16. 22. pro 2019.

    A nice trick to share, it is pretty easy to learn syntax via bucklescript command line tools, see the pic attached

    Prikaži ovu nit
    Poništi
  17. proslijedio/la je Tweet
    21. pro 2019.
    Poništi
  18. proslijedio/la je Tweet
    18. pro 2019.
    Poništi
  19. 17. pro 2019.

    A difference between BuckleScript and other compilers, we not only want to provide great abstraction but low (zero) cost abstraction, I still remember vividly the quote I read when learning common lisp -- 'Lisp programmers know the value of everything and the cost of nothing.'"

    Poništi
  20. 17. pro 2019.

    Working on the last release of BuckleScript in 2019, as a gift for New Year, we will ship zero cost abstraction for high rank polymorphism and existential type encoding(great for JS interop) The compiler improved a lot this year, try in 2020!

    Poništi

Čini se da učitavanje traje već neko vrijeme.

Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.

    Možda bi vam se svidjelo i ovo:

    ·