-
Notifications
You must be signed in to change notification settings - Fork 13.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
--shared should be a crate directive #360
Comments
Really? Is there a reason for this? Last time I tried, simply adding a metadata name to rustc made it loadable as a library. I think this is a great property to have -- allow people to include little main procs in their libraries for running them as stand-alone programs. |
Err. Didn't mean to close. |
Hmm, you have a good point. It would be nice to be able to specify that a crate is default-shared or default-executable in the |
I was thinking of implementing by just checking for main. If it exists, it is a program, if not, it is a library. |
OK, looks like we are already doing the right thing. The use case is: *) There is a nice stand alone program that does something you would like to have as part of your program. |
Add sem_timedwait for unix platforms
…y-and-privacy Fix grammar in the "Visibility and Privacy" section
…2529c0 Bump gimli from `8f47f31` to `e2529c0`
* Handle LLVM 13 release * Bump for LLVM 14
Add scalar shifts
--shared
violates the design because every crate is either shared or isn't. This should be a crate directive.The text was updated successfully, but these errors were encountered: