|
7 posts total
 How times change. Long ago programs tended to have fixed limits for things. Then the GNU Coding Standards came along and recommended avoiding arbitrary limits, and using things like dynamic allocation instead. Now that everything is under attack and fuzzing and etc., we are putting limits back in everything. Flexible software, able to take advantage of huge machines, but with safety valves.
Show previous comments
 -v --verbose Rustifying libipuz: character sets - https://viruta.org/rustifying-libipuz-charset.html Rustificar libipuz: conjuntos de caracteres - https://viruta.org/rustifying-libipuz-charset-es.html Well well well, turns out that the GCC backend for Rust detects some errors that plain Rust doesn't! https://gitlab.gnome.org/GNOME/librsvg/-/issues/1055 I wonder if this sort of thing would be caught by Miri.  @federicomena Interesting. I'd generally expect miri to detect more things than this would, but this would work for things miri doesn't support (like code using ffi).  Would love to hear stories from #mozilla people who were involved in implementing the layout tree / render tree. I'm doing that for librsvg and woah, it's a lot of work. |
Gregory's Server
@federicomena Honest fixed limits were better than dishonest no limits. But honest flexible limits are better still.