# Today's Qi meeting notes

**URL:** https://racket.discourse.group/t/todays-qi-meeting-notes/2323
**Category:** General
**Tags:** event, qi
**Created:** [September 17, 2023, 5:25pm UTC](https://racket.discourse.group/t/todays-qi-meeting-notes/2323 "2023-09-17T17:25:43Z")
**Posts on this page:** 1
**Showing post:** 14

<div class="post-metadata">

### Author: ![countvajhula](https://yyz2.discourse-cdn.com/free1/user_avatar/racket.discourse.group/countvajhula/32/65_2.png) [@countvajhula](https://racket.discourse.group/u/countvajhula)
#### Post date: [November 19, 2023, 5:27am UTC](https://racket.discourse.group/t/todays-qi-meeting-notes/2323/14 "2023-11-19T05:27:58Z")

</div>

Friday's notes:

[Rogue's Gambit](https://github.com/drym-org/qi/wiki/Qi-Compiler-Sync-Nov-17-2023)

Highlights:

- Dominik gave an awesome demo of the Racket Roguelike Library
- Brad (@Gambiteer ), author of SRFI 231, described at a high level a deforestation-like approach in generalized arrays
- Why bother deforesting `range` when it doesn't improve performance on its own?
- Why do we still need `begin-encourage-inline` when we have already said `define-inline`? (we don't know. Any ideas?)
- The huge potential of Qi's "no accidental side effects" policy

We also finally returned to [the discussion about good ways to test the compiler](https://racket.discourse.group/t/best-practices-for-testing-compiler-optimizations/2369), and adopted a clever technique suggested by @samth and @gus-massa to [test the compiler's initial normalization pass](https://github.com/drym-org/qi/pull/115/commits/317173f6d90b64e816fb0b29ca040849f45979d8). We're going to continue exploring this next time so you're welcome to join if you're interested in either sharing or learning more here.

---

_[View the full topic](https://racket.discourse.group/t/todays-qi-meeting-notes/2323)._