From 99f05600aed58a7d625e9e618e571fe25c33e6b4 Mon Sep 17 00:00:00 2001 From: Micah Date: Thu, 2 Jan 2025 15:02:47 -0800 Subject: [PATCH] Fix grammar --- docs/function-eprint.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/function-eprint.md b/docs/function-eprint.md index 969fe37..e6fcab0 100644 --- a/docs/function-eprint.md +++ b/docs/function-eprint.md @@ -23,7 +23,7 @@ A global `eprint` would be added to the global environment. It would have the sa - Python has `print` designed around this passing stream handles: `print(...)` prints to `stdout` and `print(..., file=sys.stderr)` prints to `stderr` - C has `fprintf` that works similiar to Python's `print`: `printf(stdout, ...)` and `printf(stderr, ...)` -These are just examples. Based on further research on this that it seems roughly split between functions that accept a stream handle to write in (like C or Python) and those that use globals (like JavaScript or Rust). Given Luau currently has no concept of stream handles and `print` already exists, it seems more reasonable to propose the latter. +These are just examples. Based on further research on this, it seems roughly split between functions that accept a stream handle to write in (like C or Python) and those that use globals (like JavaScript or Rust). Given Luau currently has no concept of stream handles and `print` already exists, it seems more reasonable to propose the latter. By default, `stderr` is generally not buffered in the same way as `stdout`. This RFC acknowledges this, but does not specify whether `stderr` should be changed to buffer or not: this is likely better left to the embedder rather than decided by Luau itself.