racket / racket/typed-racket

Generated contracts for polymorphic vector types need to use impersonator contracts, not chaperone contracts

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

Nobody has claimed this yet.

Dominant language
Racket
Stars
575
Forks
106
Avg merge
2h 1m
Merged PRs (30d)
2

Description

This program fails with a contract error:

#lang typed/racket

(require/typed
 racket/base
 [vector-ref (All [a] (Vectorof a) Integer -> a)])

(vector-ref (vector 1 2 3) 1)
vector-ref: non-chaperone result;
 received a result that is not a chaperone of the original result
  original: 2
  received: #<a4>

I think the generated contract that wraps the vector value needs to be an impersonator contract, not a chaperone contract.

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 reproducing the typed/racket example from the issue and trace how the generated contract for (Vectorof a) is chosen for vector-ref. Compare the chaperone and impersonator behavior involved in the contract error. Done means the example evaluates without the reported non-chaperone result error.

Written by the indexing model from the issue text.

Assessment

Domain
compilers
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 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.