rocq-prover / rocq-prover/stdlib

Confusing warning: Using Vector.t is known to be technically difficult

Open
#5 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Rocq Prover
Stars
42
Forks
38
Avg merge
14h 6m
Merged PRs (30d)
3

Description

Description of the problem

I was greeted with this warning:

Using Vector.t is known to be technically difficult, see <https://github.com/coq/coq/blob/master/theories/Vectors/Vector.v>.
[warn-library-file-stdlib-vector,stdlib-vector,warn-library-file,user-warn,default]

The message is ominous and unhelpful, as there is no course of action being proposed and the problem of difficulty is subjective. Furthermore, the URL is missing (404).

  • Is the Vector library being deprecated?

I also am greeted with this warning:

Consider [list bool] instead. See <https://github.com/coq/coq/blob/master/theories/Vectors/Vector.v> for details. Please open an issue if you would like to keep using Bvector.

I am not sure what is the intent behind the suggestion to use list bool.

I would be happy to submit a pull request on improving the warning message, and getting some clarity on the issue.

Thanks!

Small Rocq / Coq file to reproduce the bug

No response

Version of Rocq / Coq where this bug occurs

8.20

Last version of Rocq / Coq where the bug did not occur

No response

Contributor guide

Open the contributing guide

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 inspecting theories/Vectors/Vector.v and the warning text for Vector.t and Bvector, including the referenced URL. Clarify whether the Vector library or Bvector is deprecated, then update the messages so their intent, suggested action, and valid reference are explicit; done means the warnings no longer point to a 404 and explain the list bool recommendation.

Written by the indexing model from the issue text.

Assessment

Domain
tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.