various grammar improvements by Mr-Potato-l · Pull Request #37 · julelang/manual

Mr-Potato-l · 2026-02-10T14:46:05Z

compiler
getting-started
low-level-helpers
project
runtime
some-questions

koibtw

reviewed first 7 files

koibtw · 2026-02-10T14:50:09Z

src/compiler/backend/cpp-backend-compilers/clang.md

 # Clang

-Clang is a C/C++ compiler using LLVM. Jule gives priority support to Clang and is recommended to be used with Clang whenever possible. Jule and related projects use Clang as the backend compiler and are primarily tested for Clang.
+Clang is a C/C++ compiler using LLVM. Jule gives priority support to Clang and it's recommended to be used with Clang whenever possible. Jule and related projects use Clang as the backend compiler and are primarily tested for Clang.


i think this one is fine actually

koibtw · 2026-02-10T14:52:30Z

src/compiler/backend/cpp-backend-compilers/index.md

 ### Primary Support

-Primary support are primarily supported, most important and most recommended compilers. When a problem occurs in these compilers, priority is given to the solution and it is tried to be solved quickly.
+Primary support is the primarily supported, most important and most recommended compilers. When a problem occurs in these compilers, priority is given to the solution and it is tried to be solved quickly.


Suggested change

Primary support is the primarily supported, most important and most recommended compilers. When a problem occurs in these compilers, priority is given to the solution and it is tried to be solved quickly.

Primary support refers to the most important and recommended compilers. When a problem occurs with these compilers, it is given priority and addressed as quickly as possible.

koibtw · 2026-02-10T14:55:21Z

src/compiler/backend/cpp-backend-compilers/index.md

 ### Partial Support

-Partial support is compilers that are officially supported but not always guaranteed to be as accurate as primary supported compilers. Even if they can compile your code, there is also no guarantee that the executable will execute as expected.
+Partial support is compilers that are officially supported but not always guaranteed to be as accurate as primary support compilers. Even if they can compile your code, there is no guarantee that the executable will run as expected.


Suggested change

Partial support is compilers that are officially supported but not always guaranteed to be as accurate as primary support compilers. Even if they can compile your code, there is no guarantee that the executable will run as expected.

Partial support covers compilers that are officially supported but offer lower accuracy and reliability than primary support compilers. Code may compile successfully, but correct runtime behavior is not guaranteed.

koibtw · 2026-02-10T15:19:27Z

src/compiler/compiling/using-julec.md

 In compile mode, julec will show you the build command itself on the command line, which is used during compilation. You can also set the mod to transpile and choose to compile manually, or you can write a script that compiles the code after you have it in C++ form, using the transpile mode to experience compile mode.

-As result we have a executable machine code result of our program.
+As a result we have an executable machine code result of our program.


Suggested change

As a result we have an executable machine code result of our program.

As a result, we get an executable machine code of our program.

koibtw · 2026-02-10T15:20:38Z

src/compiler/basic-commands.md


 ## help
-Shows help about of commands.
+Shows help about different commands.


Suggested change

Shows help about different commands.

Shows command-specific help.

koibtw · 2026-02-10T15:21:32Z

src/compiler/basic-commands.md


 ## env
-Show information about jule environment.
+Show information about the jule environment.


Suggested change

Show information about the jule environment.

Shows information about the jule environment.

koibtw · 2026-02-10T15:22:21Z

src/compiler/compiler-optimizations.md

+Enables special optimizations for the built-in `append` function.

- It prevents the allocating and destruction of a new slice by adding slice literals element-by-element if append used at single assignment statement.
+- It prevents the allocating and destruction of a new slice by adding slice literals element-by-element if append is used at single assignment statement.


Suggested change

- It prevents the allocating and destruction of a new slice by adding slice literals element-by-element if append is used at single assignment statement.

- Prevents allocating and destruction of a new slice by adding slice literals element-by-element if append is used at single assignment statements.

koibtw · 2026-02-10T15:22:39Z

src/compiler/compiler-optimizations.md


 - Simplifies expressions such as `len([]byte(myStr))` to `len(myStr)`.
- Converts expressions such as `len([]rune(myStr))` to more efficient variant which is avoids making allocation.
+- Converts expressions such as `len([]rune(myStr))` to a more efficient variant which avoids making allocation.


Suggested change

- Converts expressions such as `len([]rune(myStr))` to a more efficient variant which avoids making allocation.

- Converts expressions such as `len([]rune(myStr))` to a more efficient variant which avoids allocation.

koibtw · 2026-02-10T15:24:12Z

src/compiler/compiler-optimizations.md


 - Removes unreachable if-else chain cases such as having constant false expressions. Applied for if-else chains, and match-cases.
- Remove unnecessary trailing cases that comes after constant true case. Applied for if-else chains, and match-cases.
+- Removes unnecessary trailing cases that come after constant true case. Applied for if-else chains, and match-cases.


Suggested change

- Removes unnecessary trailing cases that come after constant true case. Applied for if-else chains, and match-cases.

- Removes unnecessary trailing cases that come after constant true cases. Applied for if-else chains and match-cases.

koibtw · 2026-02-10T15:24:59Z

src/compiler/compiler-optimizations.md

- Avoids using wrapper for strings if string compared with literal.
- Eliminates and simplifies predictable boolean expressions. Such as `if (x || true)` will be handled as `if (true)` or `if (x && false)` will be handled as `if (false)`.
- Eliminates predictable comparison expressions. Such as `if (x > x)` will be handles ad `if (false)` or `if (x == x)` will be handled as `if (true)`.
+- Avoids using a wrapper for a string if the string is compared with a literal.


Suggested change

- Avoids using a wrapper for a string if the string is compared with a literal.

- Avoids using wrapping strings compared with literals.

mertcandav

Generally looks good to me.
But please remember to update the jump-table of the Some Questions section.

mertcandav · 2026-02-10T15:44:33Z

src/some-questions.md

 - [Why does Jule use exceptionals instead of other error handling methods?](#why-does-jule-use-exceptionals-instead-of-other-error-handling-methods)
 - [Why do exceptionals not support combining?](#why-do-exceptionals-not-support-combining)
 - [Will Jule always use C++ as backend?](#will-jule-always-use-c-as-backend)
 - [Why does not Jule have built-in methods?](#why-does-not-jule-have-built-in-methods)


Suggested change

- [Why doesn't Jule have built-in methods?](#why-doesn-t-jule-have-built-in-methods)

mertcandav · 2026-02-10T15:46:30Z

src/some-questions.md

 - [Why is `self` the only receiver parameter?](#why-is-self-the-only-receiver-parameter)
 - [Why are some packages in the standard library adopted from Go?](#why-are-some-packages-in-the-standard-library-adopted-from-go)
 - [Why were default field values removed?](#why-were-default-field-values-removed)
 - [Why do not captured variables of closures need to be specified?](#why-do-not-captured-variables-of-closures-need-to-be-specified)


Suggested change

- [Why don't captured variables of closures need to be specified?](#why-don-t-captured-variables-of-closures-need-to-be-specified)

mertcandav · 2026-02-10T15:47:54Z

src/some-questions.md

 - [Why are some packages in the standard library adopted from Go?](#why-are-some-packages-in-the-standard-library-adopted-from-go)
 - [Why were default field values removed?](#why-were-default-field-values-removed)
 - [Why do not captured variables of closures need to be specified?](#why-do-not-captured-variables-of-closures-need-to-be-specified)
 - [Why do not allow choose how to capture variables of closures?](#why-do-not-allow-choose-how-to-capture-variables-of-closures)


Suggested change

- [Why is choosing how to capture variables of closures not allowed?](#why-is-choosing-how-to-capture-variables-of-closures-not-allowed)

mertcandav · 2026-02-10T15:49:00Z

src/some-questions.md

 - [Why were default field values removed?](#why-were-default-field-values-removed)
 - [Why do not captured variables of closures need to be specified?](#why-do-not-captured-variables-of-closures-need-to-be-specified)
 - [Why do not allow choose how to capture variables of closures?](#why-do-not-allow-choose-how-to-capture-variables-of-closures)
 - [Why the function keyword needed for short function literals?](#why-the-function-keyword-needed-for-short-function-literals)


Suggested change

- [Why is the function keyword needed for short function literals?](#why-is-the-function-keyword-needed-for-short-function-literals)

mertcandav · 2026-02-10T15:49:38Z

src/some-questions.md

 - [Why do not captured variables of closures need to be specified?](#why-do-not-captured-variables-of-closures-need-to-be-specified)
 - [Why do not allow choose how to capture variables of closures?](#why-do-not-allow-choose-how-to-capture-variables-of-closures)
 - [Why the function keyword needed for short function literals?](#why-the-function-keyword-needed-for-short-function-literals)
 - [Why mutability is not handled automatically for parameters of short function literals?](#why-mutability-is-not-handled-automatically-for-parameters-of-short-function-literals)


Suggested change

- [Why is mutability not handled automatically for parameters of short function literals?](#why-is-mutability-not-handled-automatically-for-parameters-of-short-function-literals)

Mr-Potato-l added 6 commits February 10, 2026 14:20

Improved grammar in main uncategorized tabs.

0ac237c

Improved grammar in the "Getting Started" section.

500ecd4

Improved grammar in the "Project" section.

d56844d

Improved grammar in the "Runtime" section.

78084dc

Improved grammar in the "Low-Level Helpers" section.

069af07

Improved grammar in the "Compiler" section.

9425e47

koibtw changed the title ~~Improved grammar in 6 sections!~~ various grammar improvements Feb 10, 2026

koibtw requested changes Feb 10, 2026

View reviewed changes

mertcandav requested changes Feb 10, 2026

View reviewed changes

	Primary support is the primarily supported, most important and most recommended compilers. When a problem occurs in these compilers, priority is given to the solution and it is tried to be solved quickly.
	Primary support refers to the most important and recommended compilers. When a problem occurs with these compilers, it is given priority and addressed as quickly as possible.

	Partial support is compilers that are officially supported but not always guaranteed to be as accurate as primary support compilers. Even if they can compile your code, there is no guarantee that the executable will run as expected.
	Partial support covers compilers that are officially supported but offer lower accuracy and reliability than primary support compilers. Code may compile successfully, but correct runtime behavior is not guaranteed.

	As a result we have an executable machine code result of our program.
	As a result, we get an executable machine code of our program.

	Shows help about different commands.
	Shows command-specific help.

	Show information about the jule environment.
	Shows information about the jule environment.

	- It prevents the allocating and destruction of a new slice by adding slice literals element-by-element if append is used at single assignment statement.
	- Prevents allocating and destruction of a new slice by adding slice literals element-by-element if append is used at single assignment statements.

	- Converts expressions such as `len([]rune(myStr))` to a more efficient variant which avoids making allocation.
	- Converts expressions such as `len([]rune(myStr))` to a more efficient variant which avoids allocation.

	- Removes unnecessary trailing cases that come after constant true case. Applied for if-else chains, and match-cases.
	- Removes unnecessary trailing cases that come after constant true cases. Applied for if-else chains and match-cases.

	- Avoids using a wrapper for a string if the string is compared with a literal.
	- Avoids using wrapping strings compared with literals.


	- [Why doesn't Jule have built-in methods?](#why-doesn-t-jule-have-built-in-methods)


	- [Why don't captured variables of closures need to be specified?](#why-don-t-captured-variables-of-closures-need-to-be-specified)


	- [Why is choosing how to capture variables of closures not allowed?](#why-is-choosing-how-to-capture-variables-of-closures-not-allowed)


	- [Why is the function keyword needed for short function literals?](#why-is-the-function-keyword-needed-for-short-function-literals)


	- [Why is mutability not handled automatically for parameters of short function literals?](#why-is-mutability-not-handled-automatically-for-parameters-of-short-function-literals)

Conversation

Mr-Potato-l commented Feb 10, 2026 • edited by koibtw Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

koibtw left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

mertcandav left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Mr-Potato-l commented Feb 10, 2026 •

edited by koibtw

Loading