`new F().x` is parsed as `new (F().x)` instead of `(new F()).x`

Open
  • Is something wrong?
#87 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start by finding the parser entry point for new expressions and how it handles following member access or indexing; the issue does not name files or tests. Use the supplied Rascal snippet as a reproducer and compare new F().proto with (new F()).proto; done means the unparenthesized property and index forms behave as expected.

Written by the indexing model from the issue text.

Description

Version: 0.3.6

When compiling the following code with Rascal and running:

function F() {
    trace("F called, this is " + (this == _root ? "_root" : "new object"));
    this.prop = "prop";
}
F.prototype.proto = "proto";

trace(new F().proto);      // "undefined", expected "proto"
trace((new F()).proto);    // "proto", as expected
trace(new F().prop);        // "underfined", expected "prop"
trace(new F()["proto"]);   // "undefined", expected "proto"
Dominant language
Rust
Stars
22
Forks
2
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 Dinnerbone/Rascal

All issues in Dinnerbone/Rascal

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.