joliss

kanji-gpt main [!] ♥ ka 練 習
Fetching https://jpdb.io/kanji/練?expand=v
Words for kanji 練:
1094 2715 2717  練習    practice; training; drill; (an) exercise; workout
 558 1836 1789  訓練    training; drill; practice; discipline
 502  194  231  洗練    polish; refinement
 216  169  229  熟練    skill; dexterity; proficiency
  73   92   93  試練    test; trial; probation; ordeal; tribulation
  36   34   39  練る    to knead; to thicken into a paste (stirring over a flame); to polish (a plan, etc.); to refine; to train; to drill; to gloss (silk)

joliss

sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs (rw,nosuid,noexec,relatime,size=32823540k,nr_inodes=8205885,mode=755,inode64)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,nodev,noexec,relatime,size=6584460k,mode=755,inode64)
/dev/mapper/ubuntu--vg-ubuntu--lv on / type xfs (rw,noatime,attr2,inode64,logbufs=8,logbsize=32k,noquota)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,inode64)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k,inode64)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,size=4096k,nr_inodes=1024,mode=755,inode64)

joliss

> @architect/[email protected] test /home/ubuntu/src/architect-sandbox
> npm run lint && npm run test:integration && npm run coverage


> @architect/[email protected] lint /home/ubuntu/src/architect-sandbox
> eslint . --fix


> @architect/[email protected] test:integration /home/ubuntu/src/architect-sandbox

joliss

update src/http/get-get-normal/node_modules/@architect/shared/package-lock.json
update src/http/get-get-normal/node_modules/@architect/shared/package.json
update src/http/get-get-normal/node_modules/@architect/shared/cache
update src/http/get-get-normal/node_modules/@architect/shared/constants
update src/http/get-get-normal/node_modules/@architect/shared/datetime
update src/http/get-get-normal/node_modules/@architect/shared/utils
update src/http/get-get-normal/node_modules/@architect/shared/node_modules
update src/http/get-get-normal/node_modules/@architect/shared/sources
remove src/http/get-get-normal/node_modules/@architect/shared/shared
update src/http/get-get-normal/node_modules/@architect/shared/cache/_convert-timestamp.js

joliss

Andalusia, Spain
Aragon, Spain
Asturias, Spain
Balearic Islands, Spain
Canary Islands, Spain
Cantabria, Spain
Castile-La Mancha, Spain
Castile and León, Spain
Catalonia, Spain
Ceuta, Spain

joliss

joliss

// let's turn Promise and List into Monads

Promise::bind (then but must get promise)
List::bind (flatmap)

Promise::pure = Promise.resolve
List::pure = [x]

// This works in JS:
map(f: Fn, m: Monad) {

joliss

How about having "parent objects" instead of "lifetimes"?

Language design question: I wonder if we can replace or supplant the notion of "lifetimes" in languages like Rust with a notion of "parent objects" (or "context objects").

In Rust (and most languages), iterators into vectors are (ptr, end) pairs. Having a notion of "parent" objects allows us to make them plain ptr values, and additionally allows for safely appending to vectors while iterating.

Some background first. In Rust, iterators into vectors (technically, into slices) are internally represented as (ptr, end) pairs. Thus if we create an iterator,

let mut i = vec.iter();

joliss

#!/usr/bin/node

const N = 1000000;

// 130 ms
(function() {
  console.time('+=');
  let a = '';
  for (let i = 0; i < N; i++) {
    a += 'x';

joliss

// module: fso, for in-memory file system objects

// FSObject is the raw object that will be part of the
// internal Broccoli plugin API. Need better name?
// (Git terminology: File = blob, Directory = tree,
// FSObject = object.)

class FSObject { }

class File extends FSObject {