Skip to content

[Docs] Eval on checkbox toggle on - #644

Merged
bobzhang merged 1 commit into
rescript-lang:gh-pagesfrom
chenglou:eval-upon-click
Aug 15, 2016
Merged

bobzhang merged 1 commit into
rescript-lang:gh-pagesfrom
chenglou:eval-upon-click

Conversation

@chenglou

Copy link
Copy Markdown
Member

Editor happened to strip the trailing whitespace if you don't mind.

(I also changed the "Eval" label into "Evaluate" instead. Slightly clearer for newcomers that it's not a technical OCaml concept e.g. "turn on eval").

@bobzhang

Copy link
Copy Markdown
Member

This looks good to me, but there are merge conflicts

@chenglou

Copy link
Copy Markdown
Member Author

Ah because #645 got merged first, sec.

(I also changed the "Eval" label into "Evaluate" instead. Slightly clearer for newcomers that it's not a technical OCaml concept e.g. "turn on eval").
@chenglou

chenglou commented Aug 15, 2016 •

Copy link
Copy Markdown
Member Author

Done. Whitespace-insensitive diff view: https://github.com/bloomberg/bucklescript/pull/644/files?w=1

@bobzhang

Copy link
Copy Markdown
Member

Thanks, FYI, I am working on sharing the same code base (#611) between reason and OCaml playground

@bobzhang
bobzhang merged commit a7f0a31 into rescript-lang:gh-pages Aug 15, 2016
@chenglou
chenglou deleted the eval-upon-click branch August 15, 2016 19:50
@chenglou

chenglou commented Aug 15, 2016 •

Copy link
Copy Markdown
Member Author

Hah, thanks for notifying, because I was gonna work on that right now. Would a toggle be enough? On the same page?

Edit: just saw your dropdown comment. Cool!

@bobzhang

Copy link
Copy Markdown
Member

I think so -- would you mind split some workload, I will create a submodule to upgrade reason parser, is that good?

@chenglou

Copy link
Copy Markdown
Member Author

I'll put the toggle and make it work with the existent code?

@bobzhang

Copy link
Copy Markdown
Member

Also the reason examples need be updated too

cknitt added a commit that referenced this pull request Oct 23, 2026
…es (#8990)

Why:
    The same logic was kept in several copies that had to change together.
    Misc.find_map_in_path_uncap is now the one "name as written, then
    uncapitalized" lookup, used by Misc.find_in_path_uncap, Config_util
    and Bs_cmi_load (#8925 had changed all three). Editor completion prints
    polyvariant labels with Res_printer.print_poly_var_ident instead of a
    copy of the printer's classifier, which had drifted. Lam_check and
    Lam_dce use Hash_ident, which Hash_set_ident duplicated since #8787.

Format modified (completion label of a polymorphic variant):
Example:
    type t = [#644 | #""]
    let f = (e: t) => ignore(e)
    // f()
    //   ^com
Before (text):
    #"644"
    #
After (text):
    #644
    #""



Claude-Session: https://claude.ai/code/session_01Xk6AeCYpCK4SZRtHYKHGoe

Signed-off-by: Christoph Knittel <ck@cca.io>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
aspeddro pushed a commit to aspeddro/rescript-compiler that referenced this pull request Oct 31, 2026
…es (rescript-lang#8990)

Why:
    The same logic was kept in several copies that had to change together.
    Misc.find_map_in_path_uncap is now the one "name as written, then
    uncapitalized" lookup, used by Misc.find_in_path_uncap, Config_util
    and Bs_cmi_load (rescript-lang#8925 had changed all three). Editor completion prints
    polyvariant labels with Res_printer.print_poly_var_ident instead of a
    copy of the printer's classifier, which had drifted. Lam_check and
    Lam_dce use Hash_ident, which Hash_set_ident duplicated since rescript-lang#8787.

Format modified (completion label of a polymorphic variant):
Example:
    type t = [rescript-lang#644 | #""]
    let f = (e: t) => ignore(e)
    // f()
    //   ^com
Before (text):
    #"644"
    #
After (text):
    rescript-lang#644
    #""

Claude-Session: https://claude.ai/code/session_01Xk6AeCYpCK4SZRtHYKHGoe

Signed-off-by: Christoph Knittel <ck@cca.io>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: Pedro Castro <aspeddro@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants