useSubscription and useMutableSource1 tearing and deopt behavior.
The tree below represents a React application mounting. During mount, two components read from an external, mutable source. The first one (List) reads version 1 of that data and the second one (Item) reads version 2.
N/A.
Copyright © <year> <copyright holders>
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
| const getDSLValue = (iterator, last) => { | |
| const {value, done} = iterator.next(last); | |
| if (done) { | |
| return value.slice(1).reduce((x, f) => f(x), value[0]); | |
| } | |
| return getDSLValue(iterator, last ? [...last, value] : [value]); | |
| } | |
| const pipe = gen => getDSLValue(gen(null, )); |
| const getDSLValue = (iterator, last) => { | |
| const {value, done} = iterator.next(last); | |
| if (done) { | |
| return value; | |
| } | |
| switch (value) { | |
| case 'sword': { | |
| return getDSLValue(iterator, { | |
| weaponType: "Shiny Sword", |
| const interpret = iterator => last => { | |
| const {value, done} = iterator.next(last); | |
| return (done) ? Promise.resolve(value) : value.then(interpret(iterator)); | |
| }; | |
| const asyncAwait = g => interpret(g())(); | |
| // ... Usage ... | |
| const addOneSoon = (x, t) => new Promise(resolve => { |
| "workbench.colorCustomizations": { | |
| // Contrast Colors - The contrast colors are typically only set for high contrast themes. If set, they add an additional border around items across the UI to increase the contrast. | |
| "contrastActiveBorder": "", | |
| "contrastBorder": "", | |
| // Base Colors | |
| "focusBorder": "", | |
| "foreground": "", | |
| "widget.shadow": "", | |
| "selection.background": "", | |
| "descriptionForeground": "", |
I made a documentation generator that cashes in on Clojure's dynamism. See the play-cljs docs (a ClojureScript game library) for an example of its output.
Like many of you, I've often wondered what my final regret will be on my deathbed. My best guess came to me in a dream recently. I was walking across the charred earth of an apocalyptic future world, maneuvering around the remains of the less fortunate. I was startled to find a young girl, barely holding onto her life. She murmured something to me. I asked her to repeat it, and she said more loudly: "I...wish your Clojure projects didn't have such crappy documentation."
| /* | |
| * Concept for emulating higher-kinded types using Flow. Instead of passing | |
| * a type that has not been applied to parameters, this pattern passes | |
| * a type-level function that will map a parameter type to the desired | |
| * higher-kinded type applied to the given parameter. | |
| * | |
| * @flow | |
| */ | |
| // a higher-kinded type is represented indirectly via a type-level function from |
| (ns my.promises | |
| "Demo to show different approaches to handling promise chains in ClojureScript | |
| In particular, this file investigates how to pass data between Promise | |
| callbacks in a chain. | |
| See Axel Rauschmayer's post | |
| http://2ality.com/2017/08/promise-callback-data-flow.html for a problem | |
| statement. |
A tiny (265 byte) utility to create state machine components using two pure functions.
The API is a single function that accepts 2 pure functions as arguments:
