Why is rust nightly required

Repository metrics

Stars

59 stars (59 stars)

PR merge metrics

PR metrics pending (PR metrics pending)

Description

error: failed to run custom build command for `pear_codegen v0.1.2`
process didn't exit successfully: `/home/why/gopkg/src/github.com/filecoin-project/replication-game/target/release/build/pear_codegen-c6388815171fa35c/build-script-build` (exit code: 101)
--- stderr
Error: Pear requires a nightly or dev version of Rust.
Installed version is: 1.31.0 (2018-12-04). Minimum required: 1.31.0-nightly (2018-10-05).
thread 'main' panicked at 'Aborting compilation due to incompatible compiler.', /home/why/.cargo/registry/src/github.com-1ecc6299db9ec823/pear_codegen-0.1.2/build.rs:31:13
note: Run with `RUST_BACKTRACE=1` for a backtrace.

warning: build failed, waiting for other jobs to finish...
error: build failed

Contributor guide

Research direction

Investigate why the 'pear' crate requires a nightly version of Rust. Check the 'pear' crate documentation or source to understand the nightly features it uses. Determine if there is a stable alternative or if the project can be built with a newer stable version. Provide a clear explanation in the issue or update the documentation.

Tech stack

rust

Domain

distributed systems

Issue type

Research

DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.

2

Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.

Under 1 hour

Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.

Active

ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.

Clear

Prerequisites

Rust

Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.

75