I am trying to run a rust application but some internal dependency issue is breaking, I am new to rust so struggling to fix it. This is the issue.
Looking at the message - there is no funty with version 1.2. But there is funty with version 2.0.0, 1.1.0, 1.0.1.
It is required by bitvec.
Go into Cargo.toml of this package and try to change the bitvec (or funty if it is there) to a higher or lower version
Related
I am using VS Code 1.68.1 on Windows 10 and have installed the Haskell language support plugin. I tried to install ghcup but the installation script just fails with no error message and the IRC channel #ghcup wasn't able to help so I've given up on ghcup and decided to handle this manually. I just installed HLS 1.7.0 and pointed VS Code at it. The problem is I get an error message from VS Code:
ghcide compiled against GHC 9.2.2 but currently using 8.6.5
This is unsupported, ghcide must be compiled with the same GHC version as the project.
Upon further investigation, this seems to be complaining that the ghcide library that's a part of HLS was built using ghc 9.2.2 but my current codebase was built (by Stack) using ghc 8.6.5. At least that's my reading of it, since the HLS page itself says that 1.7.0 is compatible with 8.6.5! So my first question is how on earth am I supposed to know what version of ghc was used to build HLS, and honestly why should I care?? And my second question is, how do I find the version of HLS that's compatible with my current ghc?
(Another option is to migrate Stack from 8.6.5 to 9.2.2 but I'm not sure exactly how to do this. It appears to be just a case of changing the resolver entry in stack.yaml which is currently resolver: lts-14.21. But what do I change it to? It looks like the most recent version of LTS is 19.14 https://www.stackage.org/lts-19.14. But I'm a bit nervous about making that change since the page says ghc 9.0.2 not 9.2.2. The entire Haskell ecosystem just seems really finicky and I'm new enough to Stack that don't want to end up with a messed up Stack config and possibly in Haskell package mismatch hell.
Can anyone offer any good solutions?
I am working on a project where a dependency requires a specific nightly feature. I need to use this lib, but I am afraid that if I compile the project with nightly, I could depend on nother libraries that include another unstable feature dependency and I wouldn't be aware of that.
Is it possible to compile the library that I need using nightly (while set the nightly version to version that already merged to the release branch) to some kind of "lib.a" file, and compile the whole project on stable release while linking to "lib.a"?
No, you cannot do this.
See also:
Is there any way to get unstable features on the compiler versions in stable or beta?
Is there a way to use unstable modules from Rust stable?
Are there any plans to move the MDL version to 2.x or 1.3 works perfectly fine? I can see that some of the components that exists in the mdl-ext already exists in the 2.x version.
Short answer: yes there are plans to move to https://github.com/material-components/material-components-web.
Long answer: The intention of angular2-mdl was to provide components that are stable and can be used today without a lot of breaking changes. You may know there are material component libs for angular2 but most of them are still in beta state. Material Design Lite (getmdl.io) was a perfect match because it was already stable for a long time.
The followup version of mdl has moved to https://github.com/material-components/material-components-web. So in fact there will be no mdl version 2.x. The current version of material-components-web is 0.3.0 - e.g. not a stable version with a lot of work todo. If there is a release candidate version it is planned to provide an angular version that makes the integration as easy as possible - like the current version of angular2-mdl is for mdl version 1.3.
On the swift website you have several options / versions to choose from, but some of the packages don't seem to include swift-build, what is the reason for this?
Notably:
Swift-2.2.1 14.04 May 3
Should be similar for the version of 15.10. It does not seem to be the case with the master-branch tar-balls.
Its actually quite relevant for me to try to stay up to date as possible, since Swift reaks of memory leaks at this point in time.
The release of Swift 2.2 does not include the swift package manager, as the package manager was still too early in development to include in a release version of Swift at that point. Instead, a feature was added to the package manager to allow using the version from a 3.0 toolchain with the Swift from a 2.2 toolchain, so that people could use a more recent version of the package manager.
The Node.JS website says the current version is 0.10.26, but the git repo has much newer versions going up to 0.11.12.
Is there something wrong with the later versions, are they unstable?
Why does the website say 0.10.26 is the current version?
From the Node.js wiki:
Odd versions are unstable, even versions are stable. v0.2 and v0.4 are even/stable. v0.3 and v0.5 are odd/unstable. The current stable series is v0.10.x. The next stable series will be v0.12.x. The stable branch takes bug fixes only - it does not change the JavaScript API, addon API, nor ABI (you don't have to rebuild modules after upgrading node with-in a stable branch).
You should use stable versions for production. The web site displays prominently and gives links to download the latest stable verson.
However, if you are trying to stay ahead of the curve and prepare for the next and yet unreleased stable version, then testing against an unstable version makes sense. This is why the unstable versions are also available to developers.