Skip to content

Clean up runtime exports #1683

Closed
Closed

Description

@brson

Right now the interface presented by the runtime is very sloppy. There should basically be three categories of function:

Activity

  1. graydon commented on Feb 16, 2012

    @graydon
    Contributor

    Agreed. I'd also vaguely like to rename the term upcall to something more obvious.

  2. brson commented on Feb 16, 2012

    @brson
    ContributorAuthor

    While we're changing upcall let's also put it into the rust_ namespace. What word do you suggest to replace upcall?

  3. ghost assigned on Feb 16, 2012
  4. jamorton commented on Apr 2, 2012

    @jamorton
    Contributor

    has a word been chosen yet? I could clean this up

  5. brson commented on Apr 2, 2012

    @brson
    ContributorAuthor

    No, a word has not been chosen. In the interest of making a nice embedding API I think the naming we should use is:

    • rust_* - the public embedding API - there are no existing functions in this namespace
    • rust_builtin_* - the API used by core - this is the majority of the existing functions
    • rust_dbg_* - debug / test APIs
    • rust_upcall_* - or whatever the new word for 'upcall' is

    @graydon what's the new word for 'upcall'?

  6. brson commented on Apr 2, 2012

    @brson
    ContributorAuthor

    Though builtin is a pretty long word, maybe there's a shorter synonym

  7. bblum commented on Jul 3, 2013

    @bblum
    Contributor

    This only affects libs, so is not a backwards-compatibility issue. Renominating for feature-complete.

    Most of this will become irrelevant with the new runtime, and the rust runtime's internal interface to C library functions can probably be unstandardized. But we might still want to think about the rust interface to the rest of the stdlib.

  8. graydon commented on Jul 18, 2013

    @graydon
    Contributor

    just a bug, removing milestone/nomination.

  9. graydon commented on Jul 18, 2013

    @graydon
    Contributor

    See also #3922

  10. catamorphism commented on Sep 23, 2013

    @catamorphism
    Contributor

    Could somebody ( @brson or @bblum ?) summarize what remains to be done here?

  11. thestinger commented on Nov 15, 2013

    @thestinger
    Contributor

    The old runtime support is being removed, so cleaning it up isn't necessary anymore.

  12. added a commit that references this issue on Aug 17, 2026
  13. added 2 commits that reference this issue on Aug 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-runtimeArea: std's runtime and "pre-main" init for handling backtraces, unwinds, stack overflowsC-cleanupCategory: PRs that clean code up or issues documenting cleanup.E-easyCall for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions