GithubHelp home page GithubHelp logo

ion's People

Contributors

kodyjking avatar krisnye avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

ion's Issues

Design of Multiple inheritance of data classes

Intention is that diamond inheritance brings in at most one copy of classes fields.

class Body
    mass: >= 0
class Animal extends Body
class Robot extends Body
class Cyborg extends Animal, Robot

An instance of Cyborg would only have a single mass field.

At runtime, I'm thinking that there is a vtable where you lookup an array of field offsets for each Class where the array length == length of all that classes (and inherited) fields.

Fields should be ordered such that for many classes (all without multiple inheritance) and many fields static offsets are usable and vtables aren't needed.

Design of Memory allocation / deallocation

  • Where is it done?
  • Reference counting?
  • Ability to weakly release while allowing re-use before deallocating? (Important for design of semantic immutability performance)

Calls to polymer.removeChild freezing the app.

This was fixed in commit 3e6ccca. This report was added for posterity.

The call was failing becasue sometimes it gets called when the child
element is not present. This caused the Project pages to freeze when
loaded, requiring a refresh.

fix docs

Example syntax is the most important thing for generating interest for this sort of language. It used to be in the README, which is how I was introduced to the project. Some time later, I found myself unable to find the project, even though I knew its name.
This was due to the fact that the docs became buried in the directory structure. But not only that, they are now in a format that makes them harder to acces, and what's more, they're misreferenced in the README. This has been true for more than a few months now, and I think it's a shame, which is why I'm reporting this issue.

Please consider brining some sample syntax into the README again, and adding working hyperlinks to documents, so that one needs not dig for the source of documents, and can instead click to view them rendered.

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.