microsoft / microsoft/yardl

implement constraints

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

Nobody has claimed this yet.

Dominant language
C++
Stars
35
Forks
14
Avg merge
5d 17h
Merged PRs (30d)
1

Description

I know this is a planned feature (listed in the README), but I saw there is no issue corresponding to this yet, so decided to create one!

It'd be nice to be able to express explicit constraints such as size(vec1) == size(vec2). Or size(vec1) == element. This constraint could then be checked with a "validate" function, i.e. not during "normal" reading, as that would slow things down.

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 with the constraints entry in the README and inspect the existing schema and validation entry points. Determine how expressions such as size(vec1) == size(vec2) would be represented and where explicit validation belongs. Done means constraints can be declared and checked through the proposed validate function without affecting normal reading.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.