Manishearth

W3C teams have a tendency of scribing everytihng they do, and they're pretty effective at it.

This is not due to individuals being great at scribing: the system is set up such that even new group members will be able to scribe reasonably effectively. It's also set up such that new group members will get that opportunity soon enough.

The main thing is that "anyone can scribe": most teams avoid a designated scribe and instead designate a scribe per meeting and discussion. This works with some of the following additional structure:

• Nobody is expected to scribe and take minutes simultaneously. if the scribe wants to say something, someone else will take over. You pre-agree to who that person will be before the scribe actually says something
  • Before the discussion starts, scribe asks for an alternate
• During the discussion, scribe may use chat to say "anyone want to scribe for me when I talk in a bit" and then call out that person before speaking.

Manishearth

    Running benches/vzv.rs (/home/manishearth/dev/icu4x/target/release/deps/vzv-6bc0f6959cd3bb44)
WARNING: HTML report generation will become a non-default optional feature in Criterion.rs 0.4.0.
This feature is being moved to cargo-criterion (https://github.com/bheisler/cargo-criterion) and will be optional in a future version of Criterion.rs. To silence this warning, either switch to cargo-criterion or enable the 'html_reports' feature in your Cargo.toml.

Gnuplot not found, using plotters backend
vzv/overview            time:   [1.0805 us 1.1049 us 1.1295 us]                          
Found 30 outliers among 100 measurements (30.00%)
  5 (5.00%) low severe
  2 (2.00%) low mild
  4 (4.00%) high mild

Manishearth

Moved to https://github.com/Manishearth/sibr-vote-tally

Manishearth

#!/bin/bash
# Make it exit early if there's an error
set -e
# cd git root
pushd $(git rev-parse --show-toplevel) >/dev/null
PINKY_FILE=$(git rev-parse --git-path pinky)
# Create a new scratch index based on the existing index
cp $(git rev-parse --git-path index) ${PINKY_FILE}
# Add all files to scratch index. Use -u if you don't want to include untracked files
GIT_INDEX_FILE=${PINKY_FILE} git add .

Manishearth

Base arabic (31):
ا
ب
ت
ة
ث
ج
ح
خ

Manishearth

common stuff
-----------


Basic consonants(32):
कखगघङचछजझटठडढणतथदधनपफबभमयरलवशषसह

Weirdo that only is used in ligatures, but necessary(1)
ञ

Manishearth

diff --git a/components/script/dom/audionode.rs b/components/script/dom/audionode.rs
index e8c03fbd62..2868996876 100644
--- a/components/script/dom/audionode.rs
+++ b/components/script/dom/audionode.rs
@@ -21,7 +21,7 @@ pub static MAX_CHANNEL_COUNT: u32 = 32;
 
 #[dom_struct]
 pub struct AudioNode {
-    reflector_: Reflector,
+    eventtarget: EventTarget,

Manishearth

diff --git a/src/sudoku.rs b/src/sudoku.rs
index d3be5ff..e39c035 100644
--- a/src/sudoku.rs
+++ b/src/sudoku.rs
@@ -222,7 +222,7 @@ impl Sudoku {
             // until we can't solve any more values with this method
             let mut found = None;
 
-            for (row_i, row) in self.tiles.iter_mut().enumerate() {
+            'inner: for (row_i, row) in self.tiles.iter_mut().enumerate() {

Manishearth

[merge]
tool = mymeld
conflictstyle = diff3

[mergetool "mymeld"]
# Shows three-pane merge view with central output directly being the merged file to save
cmd = $MANISHMELD $LOCAL $BASE $REMOTE --output=$MERGED
#cmd = meld "$LOCAL" "$BASE" "$REMOTE"

Manishearth

Summary

Add the ability to create custom profiles in Cargo.toml, to provide further control over how the project is built. Allow overriding profile keys for certain dependency trees.

Motivation

Currently the "stable" way to tweak build parameters like "debug symbols", "debug assertions", and "optimization level" is to edit Cargo.toml.