Le 6 août 2015 à 04:20, Glen Huang curvedm...@gmail.com a écrit :
promises are fundamentally about chaining data together, not about listening
for events.
IMHO, promises are more about reacting to state change and pass down that
reaction. And the reaction I'm proposing to add is no
Hi Sebastien,
Looks like JSPM/SystemJS can do all the things I was looking for. Have to
spend some time to read more about time.
Anyway, thanks for your help and feedback.
On Sun, Aug 2, 2015 at 10:38 PM Sébastien Cevey seb.ce...@guardian.co.uk
wrote:
On Fri, 31 Jul 2015 at 11:50 Behrang
So basically we could use it like this:
function aFunc(aParam) {
throw new Error(nameof(aParam));
}
and nameof(aParam) would return the string aParam.
This is possible to do even right now using arguments.callee and some hacky
code, but having it built-in to spec would be nicer IMHO.
--
On 8/7/15, Behrang Saeedzadeh behran...@gmail.com wrote:
Hi Sebastien,
Guys —
On Sun, Aug 2, 2015 at 10:38 PM Sébastien Cevey seb.ce...@guardian.co.uk
wrote:
[...]
Versions can be specified either at the top-level config, or even at the
import level, e.g.:
In the minutes for July 28, Rick Waldron wrote:
## 9 Tooling Updates
Ecmarkup (Emu)
- [...]
- Michael Dyck now maintaining es-spec-html, working on high-fidelity emu output
- [...]
To clarify...
Back in mid-April, I volunteered to maintain the HTML version of the ES
spec, taking over from
I still haven't looked at JSPM/SystemJS thoroughly, but regarding your
comment, I personally prefer the dependencies get resolved automatically.
For example, we can have www.example.com/app-deps.json where app-deps.json
contains something like this:
{
dependencies: [
{
6 matches
Mail list logo
