Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

round-trip issue on terms with symbolic namespace segments #3362

Closed
ceedubs opened this issue Aug 25, 2022 · 2 comments
Closed

round-trip issue on terms with symbolic namespace segments #3362

ceedubs opened this issue Aug 25, 2022 · 2 comments

Comments

@ceedubs
Copy link
Contributor

ceedubs commented Aug 25, 2022

A term like Nat.==.doc, which has a symbolic segment in its namespace (the == segment) doesn't properly round trip. See the following transcript.

```ucm
.> cd MyType.==

  ☝️  The namespace .MyType.== is empty.

```
```unison
example = "example"
```

```ucm

  I found and typechecked these definitions in scratch.u. If you
  do an `add` or `update`, here's how your codebase would
  change:
  
    ⍟ These new definitions are ok to `add`:
    
      example : ##Text

```
```ucm
.MyType.==> add example

  ⍟ I've added these definitions:
  
    example : ##Text

.MyType.==> cd .

```
```ucm
.> edit MyType.==.example

  ☝️
  
  I added these definitions to the top of
  /home/cody/code/unison/scratch.u
  
    (MyType.==.example) : ##Text
    (MyType.==.example) = "example"
  
  You can edit them there, then do `update` to replace the
  definitions currently in this namespace.

.> load scratch.u

  offset=1:
  unexpected (
  expecting ability, type, or use
      1 | (MyType.==.example) : ##Text
  

```



🛑

The transcript failed due to an error in the stanza above. The error is:


  offset=1:
  unexpected (
  expecting ability, type, or use
      1 | (MyType.==.example) : ##Text
@aryairani
Copy link
Contributor

Expected to be fixed in #3525

@runarorama runarorama removed their assignment Nov 22, 2022
@aryairani
Copy link
Contributor

It seems to have been fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants