precice / precice/rust-bindings

Option to pass custom MPI_Comm

Open
#9 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Rust
Stars
2
Forks
1
PR merge metrics
No merged PRs in 30d

Description

In the context of https://github.com/precice/precice/issues/479, I could not only find the usual constructor with the default communicator here.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading the referenced preCICE issue #479 and locating the usual constructor in the Rust bindings. Determine how a caller could supply a custom MPI_Comm; the work is done when that option is supported and its behavior is covered by relevant tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.