villander

import Controller from '@ember/controller';

export default Controller.extend({
  dates: ['2021-06-04'], // '2021-06-05', '2021-06-06']
});

villander

>>>>>>>>>>>>>>>>>>>>>>>
Teaching an IDE to understand Rust
>>>>>>>>>>>>>>>>>>>>>>>
Abstract
(A concise, engaging description for the public program. Limited to 600 characters.)

IDE support is one of Rust's most requested features. From the 2017 State of Rust Survey:
roughly 30% of Rust users are looking forward to IDE support more than any other feature in 2017 and for 22% of
non-users, lack of IDE support is their main reason for not using Rust. Thankfully, the Rust Language Server is here now and it gets smarter and
more capable every day.

villander

>>>>>>>>>>>>>>>>>>>>>>>
Teaching an IDE to understand Rust
>>>>>>>>>>>>>>>>>>>>>>>
Abstract
(A concise, engaging description for the public program. Limited to 600 characters.)

IDE support is one of Rust's most requested features. From the 2017 State of Rust Survey:
roughly 30% of Rust users are looking forward to IDE support more than any other feature in 2017 and for 22% of
non-users, lack of IDE support is their main reason for not using Rust. Thankfully, the Rust Language Server is here now and it gets smarter and
more capable every day.

villander

Ember Engines Documentation ToDos

General

• Almost all docs from README should be moved to ember-engines.com. Having similar but different info in both places is confusing and unmaintainable.

• Consider using https://github.com/ember-learn/ember-cli-addon-docs to standardize the docs and guides and to make them version-specific.

• Clarify the philosophy and intended uses for engines.

• Is the "Why Use Engines?" section on http://ember-engines.com/ sufficient?

villander

{
    // Use IntelliSense to learn about possible attributes.
    // Hover to view descriptions of existing attributes.
    // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
    "version": "0.2.0",
    "configurations": [
        {
            "type": "node",
            "request": "launch",
            "name": "Launch Program",

villander

[T]he difference between a bad programmer and a 
good one is whether he considers his code or his 
data structures more important. Bad programmers 
worry about the code. Good programmers worry about 
data structures and their relationships. 
-- Linus Torvalds
~~~
Clarity and brevity sometimes are at odds. 
When they are, I choose clarity. 
-- Jacob Kaplan-Moss

villander

/*
 * Easing Functions - inspired from http://gizma.com/easing/
 * only considering the t value for the range [0, 1] => [0, 1]
 */
EasingFunctions = {
  // no easing, no acceleration
  linear: function (t) { return t },
  // accelerating from zero velocity
  easeInQuad: function (t) { return t*t },
  // decelerating to zero velocity

villander

// install ember-cli-es6-transform

  function importFromNPM(app,moduleName) {
    let relPath = `node_modules/${moduleName}`;
    let nodePath = `./${relPath}`;
    let config = require(`${nodePath}/package.json`);

    if (config.style) {
      app.import(`${relPath}/${config.style}`);
    }

villander

import Ember from 'ember';

const { run: { debounce } } = Ember;

export default Ember.Controller.extend({
  appName:'Ember Twiddle',
  runMe() {
    console.log("I should be called once");
  },
  

villander

You can use async/await in your Ember testing suite, today! This blog post explains the situation pretty thoroughly. Also check out this blog post.

It's great in tests, but not quite useful for app code yet.

There are three ways we can get it to work. If you try async/await without any of these changes, you will get the error regeneratorRuntime is not defined.

Method	Size ※	app code	test code
includePolyfill: true	30kb	yes	yes
ember-maybe-import-regenerator	2kb	yes	yes