Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Redefinition in a view reported unresolved with two exposes and a metadata usage

Closed
  • Is something wrong?
#649 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
go
Domain
compilers

Research direction

Reproduce the example with sysml -validate using the issue's redef.sysml case and confirm that removing any one of the three triggering elements avoids the error. Trace the name-resolution path for view redefinitions, two expose statements, private imports, and metadata usage. Done means the supplied file validates without an unresolved kind reference and regression coverage preserves that behavior.

Written by the indexing model from the issue text.

Description

sysml -validate (v0.9.0, and develop with #638 applied) reports a valid redefinition as unresolved:

package Lib {
    private import ScalarValues::*;
    metadata def Tag;
    view def Dia { attribute kind : String; }
}
package P1 { private import Lib::*; }
package P2 { private import Lib::*; }
package App {
    private import Lib::*;
    view v : Dia {
        expose P1::*;
        expose P2::*;
        @Tag;
        attribute :>> kind = "grid";
    }
}

redef.sysml:14:23: error: unresolved reference: kind — did you mean Lib::Dia::kind?

It validates cleanly if you remove any one of:

  • the second expose
  • @Tag;
  • the private import Lib::*; in P1 and P2

Expected: no error. v inherits kind from Dia (OwnedRedefinition, SysML-textual-bnf :482). SysIDE accepts the file.

Dominant language
Go
Stars
24
Forks
5
Avg merge
10h 7m
Merged PRs (30d)
536

Getting set up

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 Open-MBEE/OpenSysML

All issues in Open-MBEE/OpenSysML

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.