issue-copy-test's People
issue-copy-test's Issues
Configurability of rls-blacklist
Originally created by @ (rust-dev-tools/rls-blacklist#4):
Based on reading rls-* documentation it sounded like rls blacklists are supposed to be configurable, but based on the implementation here I don't see that currently being possible. Is the goal for rls-blacklist to be configurable? via environment, config file?
Configurability of rls-blacklist
Originally created by @ (rust-dev-tools/rls-blacklist#4):
Based on reading rls-* documentation it sounded like rls blacklists are supposed to be configurable, but based on the implementation here I don't see that currently being possible. Is the goal for rls-blacklist to be configurable? via environment, config file?
Configurability of rls-blacklist
Author
Based on reading rls-* documentation it sounded like rls blacklists are supposed to be configurable, but based on the implementation here I don't see that currently being possible. Is the goal for rls-blacklist to be configurable? via environment, config file?
Another one
Originally created by @Xanewok (Xanewok/source-issue-test#2):
With body
Configurability of rls-blacklist
Originally created by @ (rust-dev-tools/rls-blacklist#4):
Based on reading rls-* documentation it sounded like rls blacklists are supposed to be configurable, but based on the implementation here I don't see that currently being possible. Is the goal for rls-blacklist to be configurable? via environment, config file?
Configurability of rls-blacklist
Originally created by @ (rust-dev-tools/rls-blacklist#4):
Based on reading rls-* documentation it sounded like rls blacklists are supposed to be configurable, but based on the implementation here I don't see that currently being possible. Is the goal for rls-blacklist to be configurable? via environment, config file?
Configurability of rls-blacklist
Originally created by @dweinstein
Based on reading rls-* documentation it sounded like rls blacklists are supposed to be configurable, but based on the implementation here I don't see that currently being possible. Is the goal for rls-blacklist to be configurable? via environment, config file?
Make -Zsave-analysis configurable
Originally created by @ (rust-dev-tools/rls-rustc#1):
Sometimes we don't want to run it, currently the shim does it every time.
Provide working usage instructions for rls-rustc
Originally created by @ (rust-dev-tools/rls-rustc#10):
I tried to use this shim, but it didn't work. Maybe I'm doing it wrong? I built it and then tried to use the generated rustc shim as a drop-in replacement for rustc to build it again.
$ cargo +nightly build --release
$ mv target target.old
$ RUSTC_WRAPPER=target.old/release/rustc cargo +nightly build
error: failed to run `rustc` to learn about target-specific information
Caused by:
process didn't exit successfully: `/Users/kats/zspace/rls-rustc/target.old/release/rustc rustc - --crate-name ___ --print=file-names --crate-type bin --crate-type rlib --crate-type dylib --crate-type cdylib --crate-type staticlib --crate-type proc-macro` (exit code: 101)
--- stderr
error: multiple input filenames provided
Also I get a different error if I run that last step without +nightly
:
$ RUSTC_WRAPPER=target.old/release/rustc cargo build
error: failed to run `rustc` to learn about target-specific information
Caused by:
process didn't exit successfully: `/Users/kats/zspace/rls-rustc/target.old/release/rustc rustc - --crate-name ___ --print=file-names --crate-type bin --crate-type rlib --crate-type dylib --crate-type cdylib --crate-type staticlib --crate-type proc-macro` (signal: 6, SIGABRT: process abort signal)
--- stderr
dyld: Library not loaded: @rpath/librustc_driver-51f1276ab2f3d846.dylib
Referenced from: /Users/kats/zspace/rls-rustc/target.old/release/rustc
Reason: image not found
I get the same errors when trying to use the shim to build other rust crates (ones that build fine with release-version rust).
Provide working usage instructions for rls-rustc
Originally created by @ (rust-dev-tools/rls-rustc#10):
I tried to use this shim, but it didn't work. Maybe I'm doing it wrong? I built it and then tried to use the generated rustc shim as a drop-in replacement for rustc to build it again.
$ cargo +nightly build --release
$ mv target target.old
$ RUSTC_WRAPPER=target.old/release/rustc cargo +nightly build
error: failed to run `rustc` to learn about target-specific information
Caused by:
process didn't exit successfully: `/Users/kats/zspace/rls-rustc/target.old/release/rustc rustc - --crate-name ___ --print=file-names --crate-type bin --crate-type rlib --crate-type dylib --crate-type cdylib --crate-type staticlib --crate-type proc-macro` (exit code: 101)
--- stderr
error: multiple input filenames provided
Also I get a different error if I run that last step without +nightly
:
$ RUSTC_WRAPPER=target.old/release/rustc cargo build
error: failed to run `rustc` to learn about target-specific information
Caused by:
process didn't exit successfully: `/Users/kats/zspace/rls-rustc/target.old/release/rustc rustc - --crate-name ___ --print=file-names --crate-type bin --crate-type rlib --crate-type dylib --crate-type cdylib --crate-type staticlib --crate-type proc-macro` (signal: 6, SIGABRT: process abort signal)
--- stderr
dyld: Library not loaded: @rpath/librustc_driver-51f1276ab2f3d846.dylib
Referenced from: /Users/kats/zspace/rls-rustc/target.old/release/rustc
Reason: image not found
I get the same errors when trying to use the shim to build other rust crates (ones that build fine with release-version rust).
Configurability of rls-blacklist
Originally created by @ (rust-dev-tools/rls-blacklist#4):
Based on reading rls-* documentation it sounded like rls blacklists are supposed to be configurable, but based on the implementation here I don't see that currently being possible. Is the goal for rls-blacklist to be configurable? via environment, config file?
Configurability of rls-blacklist
Originally created by @ (rust-dev-tools/rls-blacklist#4):
Based on reading rls-* documentation it sounded like rls blacklists are supposed to be configurable, but based on the implementation here I don't see that currently being possible. Is the goal for rls-blacklist to be configurable? via environment, config file?
Some issue
Originally created by @Xanewok (Xanewok/source-issue-test#1):
Configurability of rls-blacklist
Originally created by @ (rust-dev-tools/rls-blacklist#4):
Based on reading rls-* documentation it sounded like rls blacklists are supposed to be configurable, but based on the implementation here I don't see that currently being possible. Is the goal for rls-blacklist to be configurable? via environment, config file?
Configurability of rls-blacklist
Based on reading rls-* documentation it sounded like rls blacklists are supposed to be configurable, but based on the implementation here I don't see that currently being possible. Is the goal for rls-blacklist to be configurable? via environment, config file?
Configurability of rls-blacklist
Author dweinstein
Based on reading rls-* documentation it sounded like rls blacklists are supposed to be configurable, but based on the implementation here I don't see that currently being possible. Is the goal for rls-blacklist to be configurable? via environment, config file?
Another one
Originally created by @ (Xanewok/source-issue-test#2):
With body
Configurability of rls-blacklist
Based on reading rls-* documentation it sounded like rls blacklists are supposed to be configurable, but based on the implementation here I don't see that currently being possible. Is the goal for rls-blacklist to be configurable? via environment, config file?
Configurability of rls-blacklist
Originally created by @dweinstein (rust-dev-tools/rls-blacklist#4):
Based on reading rls-* documentation it sounded like rls blacklists are supposed to be configurable, but based on the implementation here I don't see that currently being possible. Is the goal for rls-blacklist to be configurable? via environment, config file?
Configurability of rls-blacklist
Based on reading rls-* documentation it sounded like rls blacklists are supposed to be configurable, but based on the implementation here I don't see that currently being possible. Is the goal for rls-blacklist to be configurable? via environment, config file?
Configurability of rls-blacklist
Based on reading rls-* documentation it sounded like rls blacklists are supposed to be configurable, but based on the implementation here I don't see that currently being possible. Is the goal for rls-blacklist to be configurable? via environment, config file?
Make -Zsave-analysis configurable
Originally created by @ (rust-dev-tools/rls-rustc#1):
Sometimes we don't want to run it, currently the shim does it every time.
Make -Zsave-analysis configurable
Originally created by @ (rust-dev-tools/rls-rustc#1):
Sometimes we don't want to run it, currently the shim does it every time.
Some issue
Originally created by @ (Xanewok/source-issue-test#1):
Configurability of rls-blacklist
Originally created by @ (rust-dev-tools/rls-blacklist#4):
Based on reading rls-* documentation it sounded like rls blacklists are supposed to be configurable, but based on the implementation here I don't see that currently being possible. Is the goal for rls-blacklist to be configurable? via environment, config file?
Configurability of rls-blacklist
Originally created by @ (rust-dev-tools/rls-blacklist#4):
Based on reading rls-* documentation it sounded like rls blacklists are supposed to be configurable, but based on the implementation here I don't see that currently being possible. Is the goal for rls-blacklist to be configurable? via environment, config file?
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. ๐๐๐
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google โค๏ธ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.