UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.68 Safari/537.36

Steps to reproduce the problem:
1. Define a class with a getter
2. Create instance of class
3. Access instance.getter. 
4. As soon as the . is entered after getter, the getter is called

Example: 

class SideEffectTest {
  constructor() {
    this.count = 0;
  }

  get c() {
    console.log(this.count);
    console.trace();
    this.count++
    return this.count;
  }
}

let test = new SideEffectTest()

console.assert(test.count == 0)
console.assert(test.c == 1)

// Begin typing test.c. then clear

// test.count has been incremented

console.assert(test.c == 2)
// Assertion Fails

What is the expected behavior?
There would be no side effects

What went wrong?
test.count is incremented

Did this work before? N/A 

Chrome version: 68.0.3440.68  Channel: beta
OS Version: OS X 10.12.6
Flash Version: 

Low priority in the grand scheme of things, just an interesting quirk found while testing if eager evaluation can in fact cause side effects