Skip to content

Add compilation profiles to std #7282

Closed
@brson

Description

@brson
Contributor

We would like the standard library to be compilable for multiple types of environments. Some environments (JS) don't like green threads, some (JS, microcontrollers) don't like threads at all, some (kernels) just need their own implementations of practically everything. Due to some complex interrelationships I don't think it's generally possible to factor all these capabilities out into their own crates, so we'll have to live with compiling std into different 'profiles'.

Activity

bstrie

bstrie commented on Jul 12, 2013

@bstrie
Contributor

Nominating for Well-Covered.

catamorphism

catamorphism commented on Sep 5, 2013

@catamorphism
Contributor

Just a bug

emberian

emberian commented on Sep 8, 2013

@emberian
Member

cc @cmr

alexcrichton

alexcrichton commented on Jun 10, 2014

@alexcrichton
Member

Closing, I believe that the libstd facade overrules this direction of making std more portable. Instead of having compilation profiles, we have chosen to have a "pick and choose" situation to select which crates work the best for your particular application.

added a commit that references this issue on Jun 3, 2021

Auto merge of rust-lang#7282 - camsteffen:lint-stmt-expr, r=flip1995

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 overflows

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @alexcrichton@brson@catamorphism@emberian@bstrie

        Issue actions

          Add compilation profiles to std · Issue #7282 · rust-lang/rust