Consider using const in ReSolve code more aggressively

Open
#89 0 comments 0 reactions 1 assignee View on GitHub

@pelesh is already working on this.

Since Dec 20, 2024.

Assessment

This issue has not been assessed yet.

Description

enhancement

We should probably make these pure getters const to reflect their behavior.

Originally posted by @cameronrutherford in https://github.com/ORNL/ReSolve/pull/83#discussion_r1409398505

Dominant language
C++
Stars
85
Forks
14
PR merge metrics
No merged PRs in 30d

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

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.

More from ORNL/ReSolve

All issues in ORNL/ReSolve

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.