GithubHelp home page GithubHelp logo

Comments (6)

artwyman avatar artwyman commented on May 18, 2024

I'm going to disable the canary in the test case by default, since it doesn't look like the standards committee is going to address this anytime soon. It seems more important that new users of the library can make test and run successfully the first time without being confused.

from json11.

timsong-cpp avatar timsong-cpp commented on May 18, 2024

Core issue 2137 was resolved by P0384R0 back in June 2016. The core issues list is just (very) slow to update.

from json11.

artwyman avatar artwyman commented on May 18, 2024

@timsong-cpp thanks for the update. I'm not familiar enough with terminology of the standard or the operations of the committee to be sure what that document is saying. Can you provide any color? There's a "proposed resolution" from April in a doc of "tentatively ready" issues from June. Does that mean the proposed resolution was was accepted? What does the proposed text actually mean for the example?

I'm hopeful that this might actually be a useful resolution, in which case we then only need to wait for compilers to implement the change.

from json11.

timsong-cpp avatar timsong-cpp commented on May 18, 2024

There's a "proposed resolution" from April in a doc of "tentatively ready" issues from June. Does that mean the proposed resolution was was accepted?

It was accepted. (The core - and library - working group prepares lists of ready and tentatively ready issues for each meeting for adoption by the full committee. Almost all of the time they all get adopted - and this one was, but to be sure in the general case you'd need to check a few more places.)

What does the proposed text actually mean for the example?

It reverts the DR1467 change for non-aggregate class types. Those will get the previous behavior.

from json11.

artwyman avatar artwyman commented on May 18, 2024

Ah, I didn't realize that change was a revert of the previous one, and I just educated myself on the formal definition of aggregate class, so this sounds good for json11's needs. Looking forward to seeing it implemented. Thanks.

from json11.

artwyman avatar artwyman commented on May 18, 2024

I'm pretty sure the "right" language behavior is now in all the recent compiler versions, so I'm closing this issue out.

from json11.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.