rochacbruno/py2rs

Communicating between threads is not equivalent

Open

#25 opened on Feb 2, 2018

View on GitHub
 (0 comments) (0 reactions) (0 assignees)CSS (2,049 stars) (72 forks)batch import
good first issue

Description

There’s extra output in the Rust example, and I believe the Rust example is creating a thread whereas the python example is not (although it could be implicit as I’m not familiar with Queue)

Contributor guide

Tech stack
pythonrust
Domain
documentation
Issue type
documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
basic understanding of threading in Python and Rust
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
Examine the Python and Rust code examples for thread communication, identify the extra output in the Rust example, and compare the usage of the Queue module in Python vs Rust's thread creation. Ensure the examples are equivalent in behavior.