Skip to content

Commit 7867feb

Browse files
Create 2023-01-12.md
1 parent 6496039 commit 7867feb

File tree

1 file changed

+77
-0
lines changed

1 file changed

+77
-0
lines changed

meetings/2023-01-12.md

Lines changed: 77 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,77 @@
1+
# TWG 2023-01-12
2+
3+
[Prior meeting's notes](https://github.com/haskellfoundation/tech-proposals/blob/main/meetings/2022-11-10.md)
4+
5+
## Present
6+
7+
* Hécate
8+
* John Ericson
9+
* David Thrane Christiansen
10+
* Luke McCartney
11+
* Jack K
12+
13+
## Agenda
14+
15+
### Project Updates
16+
17+
* Advisory DB
18+
* No progress right now
19+
20+
* errors.haskell.org
21+
* Now supported by GHCup and Stack
22+
23+
### Open Proposals
24+
25+
#### Haddock/GHC Decoupling
26+
27+
* Meeting tomorrow to discuss it between Hécate and Laurent
28+
29+
#### IDE/Test Integration
30+
* TODO: facilitate contact between Davean and proposal author, because Davean has a useful and relevant prototype of aspects of the proposal
31+
32+
#### Standard Library Reform Proposal
33+
https://github.com/haskellfoundation/tech-proposals/pull/47
34+
35+
* Where did the time estimate come from?
36+
* Based on work experience, done conservatively
37+
* John: How do we feel about the first step being a big boring, and having that be the only funding proposal?
38+
* David: If the first step is all that happens, have we contributed value? Is the world better, worse, or neither?
39+
* John: Mostly neither
40+
* Gershom: Even if end user experience is not better, is there a better experience for core library devs and GHC devs?
41+
* John: Hopes so
42+
* Jack: Did the overall structure change?
43+
* John: The big update is adding this "get the PR over the finish line". Also, if Safe Haskell is removed, this gets cheaper and easier.
44+
* David: Do we have feedback from GHC devs and CLC about whether their lives are better with just this first step?
45+
* John: Recall hearing back from Bodigrim, who was fairly neutral, and Ben, who was positive
46+
* Gershom: If we did Step 1, and also a little bit of Step 2 (which can be incremental) then we would get an immediate benefit because we'd have a few things that could be upgraded without reinstalling GHC.
47+
* John: Technically yes (reinstallable and upgradable) but there are some gotchas for running TH natively and ABI compat. It's unclear how much leaks into the ABI of GHC itself. But if a stage1 compiler is fine, then yes.
48+
* Gershom: What's the ABI compatibility issue?
49+
* John: TH and parts of GHCi work by loading the user program into the GHC process, and they can do whatever. If a library that GHC uses were upgraded, then that could lead to problems.
50+
* Gershom: this is surprising. If I use Bytestring 11 on a a GHC that shipped with 10 and used TH, will that cause a bug?
51+
* John: It's only if you're using these things in the Template Haskell
52+
* Gershom: You need to use the bytestring that GHC is linked against? That's a problem today, right? You're your own worst salesman.
53+
* John: Yeah, that's right
54+
* Gershom: If we do step 1 and part of 2, then many things are actually improved.
55+
* The best demonstration would be to take out things that we regret having put in `base`
56+
* Gershom: Where does that leave the proposal?
57+
* John: There's a big "future work" section at the end that isn't formally asking for money
58+
* Remaining steps:
59+
* Gershom suggestions:
60+
* Move prior work and motivation later
61+
* Put the actual proposal higher up in the document - today one must read to 6.1 to see the suggestion, and not until 7 does it say that there's no more! the first para should contain the actual concrete proposal, and then elaborate on it later (appendices, prior art, related work)
62+
* Fill out alternative prelude section
63+
* John: still needs to address David's comments
64+
65+
### Misc
66+
67+
#### Tooling thread
68+
69+
* John has made progress towards a reinstallable RTS, and triaging the details of the various configuration settings and options
70+
* This should make the bindist metadata problem less daunting and more structured
71+
* This should be generally useful for tooling
72+
73+
### Meta
74+
75+
* How did the emailed reminders work?
76+
* Decision: try again another month
77+

0 commit comments

Comments
 (0)