Files
oak-gpui/crates/gpui/src
张小白 69e76a3bb9 Refactor all_font_names (#15345)
In the current code implementation, it seems that the only difference
between `all_font_names` and `all_font_families` is whether dynamically
loaded font resources are included. Specifically, `all_font_families`
returns the names of all system fonts, while `all_font_names` includes
both the system font names and the dynamically loaded font names. In
other words, `all_font_families` is a strict subset of `all_font_names`.
This is what I observed in my tests on macOS.

<img width="682" alt="截屏2024-07-28 00 49 29"
src="https://github.com/user-attachments/assets/47317c28-0074-49d2-bcfa-052cab13e335">

Related codes:
```rust
let x: HashSet<_> = self.all_font_names().into_iter().collect();
let y: HashSet<_> = self.all_font_families().into_iter().collect();
let only_in_x = x.difference(&y).collect::<Vec<_>>();
let only_in_y = y.difference(&x).collect::<Vec<_>>();
println!("=====================================");
println!("1 -> {:?}", only_in_x);
println!("-------------------------------------");
println!("2 -> {:?}", only_in_y);
```

Release Notes:

- N/A
2024-08-23 00:11:01 +02:00
..
2024-07-22 10:46:16 -06:00
2024-08-23 00:11:01 +02:00
2024-06-18 12:16:54 -07:00
2024-03-11 10:45:57 +01:00
2024-07-03 11:28:09 -07:00
2024-08-06 16:55:51 -04:00
2024-07-22 10:46:16 -06:00
2024-07-22 10:46:16 -06:00
2024-08-23 00:11:01 +02:00
2024-07-26 16:42:21 -07:00
2024-05-29 18:06:45 -07:00