✨ fix some meeting dates, add missing meeting notes

tc39 · Feb 28, 2024 · f84d67b · f84d67b
1 parent 5d535cf
commit f84d67b
Show file tree

Hide file tree

Showing 5 changed files with 55 additions and 4 deletions.
diff --git a/meetings/notes/2021/2021-08-09.md → meetings/notes/2021/2021-09-08.md b/meetings/notes/2021/2021-08-09.md → meetings/notes/2021/2021-09-08.md
@@ -1,4 +1,4 @@
-# 09 August, 2021 Meeting Notes
+# 1st Meeting of TC39-TG3 - 2021-09-08
 
 -----
 
@@ -41,7 +41,7 @@
       1. Supply chain risk. The greatest risk that JS should address. NPM reports that only 3% are only specific to the application and 97% are libraries.
       2. Bridge to TC-53 and device security.
       3. TC-53 and Moddable have done an excellent job
-      4. Strong encapsulation is needed. Threat models are adversarial. Treat libraries as an adversary.  
+      4. Strong encapsulation is needed. Threat models are adversarial. Treat libraries as an adversary.
    3. MF:
       1. Nailing down language invariance.
       2. Explore language capabilities that are undeniable, not virtualizable.

diff --git a/meetings/notes/2021/2021-11-11.md → meetings/notes/2021/2021-11-10.md b/meetings/notes/2021/2021-11-11.md → meetings/notes/2021/2021-11-10.md
@@ -1,4 +1,4 @@
-# 11 November, 2021 Meeting Notes
+# 2nd Meeting of TC39-TG3 - 2021-11-10
 
 -----
 

diff --git a/meetings/notes/2021/2021-12-01.md b/meetings/notes/2021/2021-12-01.md
@@ -1,4 +1,4 @@
-# 01 December, 2021 Meeting Notes
+# 3rd Meeting of TC39-TG3 - 2021-12-01
 
 -----
 

diff --git a/meetings/notes/2022/2022-02-10.md b/meetings/notes/2022/2022-02-10.md
@@ -0,0 +1,4 @@
+# 4th Meeting of TC39-TG3 - 2022-02-10
+
+> [!IMPORTANT]
+> it's unclear whether this meeting took place, as the temporary notes document for it had no content and listed only the convenor as the sole attendee
diff --git a/meetings/notes/2022/2022-04-14.md b/meetings/notes/2022/2022-04-14.md
@@ -0,0 +1,47 @@
+# 5th Meeting of TC39-TG3 - 2022-04-14
+
+Jack Works - Provide an overview of the New Integrity Level
+
+Jordan - That makes sense why we wouldn’t want a protocol. If we had a protocol then we would have to verify that the users are using it correctly. There’s no way for an object to validate that my object is immutable. I think that almost every built in type should be inheritable.
+
+Mark Mill - I think the term immutable raises a bunch of issues here. Is there any invariant that you can stake across. Not useful unless you can
+
+Mathieu Hofman & Jack Work - There’s no standard for this.
+
+Jordan - The web will follow a similar pattern for it’s built-ins. We shouldn’t need 15 proposals.
+
+Mark - Harmonize this with the read-only collections proposal. Trying to find something across collections and other things. If we can find raw classes that enable describing a meaningful notion of stability.
+
+Jordan - Talking about the Built-in table Jack is showing on the screen
+
+Mark - We have to make it an open protocol, so that everything is transparent through the proxy.
+
+Jack - Would that cause problems with proxy
+
+Jordan - Proxies are already not transparent. Membrane environment - proxies are transparent
+
+Mark - The constraint that we have maintained and that I insist on. Proxies have not been transparent. Membranes enable transparency. Replacing built-ins are far beyond….
+
+Jack - …
+
+Mark - If I can freeze …
+
+Jordan -
+
+Jack - Map-sets share a similar API and can do classification on data structures.
+
+—
+
+Mark - When the map is born it is neither committed to being immutable or no longer mutable. If you opt out o
+
+Jordan - It was a mistake ES6 make on locking …
+
+–
+
+Mark - Mark suggests that we move to Zoom. That we be able to record.
+
+Mathieu - What times work best for the majority of the group.
+
+Jack Works: 8am PT works for them https://www.worldtimebuddy.com/?qm=1&lid=8,2988507,100,1816670&h=8&date=2022-4-14&sln=7-9&hf=1
+
+V8 -