Comments (6)
do you know when we can expect the next release?
Hopefully in the next 4 weeks or so. Not sure if full support for RAPs will be there by then, but I'm hoping to get at least #58 included.
from winterfell.
I am commenting here though I am not the author of the library. I believe this comes from the toolchain upgrade from 1.52.0 to 1.53.0. Which one are you using in your example above? Setting it to 1.53.0 or higher should be enough to make it compile.
Maybe adding a rust-toolchain file or specifying the supported ones in the README would be nice?
from winterfell.
I used following version:
$ rustc --version
rustc 1.52.1 (9bc8c42bb 2021-05-09)
from winterfell.
Hi @vikulin - thank you for the question!
As @Nashtare pointed out above, the issue is with the compiler version. For best results, the following compilers should be used:
- For Winterfell v0.1: rustc 1.53
- For Winterfell v0.2: rustc 1.54
@Nashtare - we are planning to move to Rust 2021 with the next release, and I believe there it should be possible to specify minimum rustc version in Cargo.toml directly. Do you think that would be sufficient?
from winterfell.
@irakliyk I didn't know they were planning to integrate this feature directly in the Cargo.toml file! I guess that will be enough then, do you know when we can expect the next release? After RAPs are integrated?
from winterfell.
Closing this out since v0.3 published today specifies rustc
version required in Cargo.toml files.
from winterfell.
Related Issues (20)
- RandomCoin trait simplification HOT 1
- Will it be made into zkvm in the future? HOT 1
- Remove duplicate query check in FRI HOT 3
- Implementing Keccak256 HOT 4
- mulfib8 example circuit is underconstrained
- `f64` field: `BaseElement` should not be convertible from `u64` or `u128` without error HOT 1
- Add serialization/deserialization for `usize` type HOT 1
- Accomodating more expressive transition constraints HOT 3
- `TraceTable::with_meta()` should be marked `unsafe`
- Suggestion: Remove outdated griffin hash implementation HOT 1
- Generalize auxiliary trace building logic HOT 2
- Simplify 2-d matrix types
- Generalize `TransitionConstraints` and `BoundaryConstraints` HOT 1
- Consider using the standard benchmark harness instead of criterion HOT 1
- DEEP polynomial with Lagrange kernel HOT 1
- `Deserializable` should have an associated type error
- `Proof::security_leve()` should take into account auxiliary proof
- `group_vector_elements` panics during account code compilation HOT 2
- Verify GKR proof in `Trace::validate()`
- FFT-based division to improve DEEP composition polynomial computation
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.
from winterfell.