I’m posting this first in the forum to see response before posting as a formal issue. Proposal This is a proposal to introduce a new keyword ends (or endall) as a terminal point to resolve the end of nested loops|conditionals. Why It’s a common code occurrence to have multiple levels of loops an…

Visually it is a good syntactic sugar and I think there is a way to call a strict rule of use (example: last open => first closed). It’s simple to understand. But on the other hand it’s a big source of mistakes. def render(truthy : Bool, show_msg : Bool = false) return "ok" if truthy thing do …

I think someone previously proposed introducing endd (two ends), enddd (three ends), etc :-)

Ok, here are 2 simple rules that control (can make more if necessary). an end statement can only resolve 1 open thing. an ends statement must resolve 2 or more open things. Thus this def render(scene, image, screenWidth, screenHeight) screenHeight.times do |y| screenWidth.times do |x| …

As long as it is not required; personally, I like 1-1 end per start of block.

Yes, I think general best practice is start with encasing a single end for each class|module|method name thing, and use ends for internal structure. But then also use it for long strings of end statements, where it’s clear they are all the same termination point for multiple things (loops|conditio…

[image] jzakiya: you would then know to unambiguously write as this (if this is what you mean). class Foo def bar while true ends if foo while true ends end If ends is used for closing 2+ open “things”, then how would it know to not also close the class in addition to bar an…

There’s too much ambiguity in Crystal to allow something like this. while, if etc can be used as suffixes which throws the whole ends thing off. It also is something that clearly cares about indentation, something I never ever ever want to see be a thing in Crystal. Also issues with begin not needin…

[image] jzakiya: Ok, here are 2 simple rules that control (can make more if necessary). an end statement can only resolve 1 open thing . an ends statement must resolve 2 or more open things . [image] jzakiya: def render(scene, image, screenWidth, screenHeight) screenHeight.times do |y…

It’s really interesting how this one simple (I thought) proposal has produced so much fear and anxiety. So let me try to lower peoples blood pressure. 1: You ARE NOT REQUIRED to ever use this. If you don’t want to use this in your code then don’t! But understand it so you can read|understand cod…

[image] jzakiya: 1: You ARE NOT REQUIRED to ever use this. If you don’t want to use this in your code then don’t! But understand it so you can read|understand code that uses it. No, but someone will, then in order to understand their code you’d have to learn it. [image] jzakiya: 2: This…

Proposal: New "ends" keyword

Community

nolyoi April 11, 2021, 9:37pm 41

I was thinking this same thing as I was reading over this. Using the ends instead of the current syntax makes it a lot less readable. Even if code could be written both ways it would hamper readability for a lot of people.

2 Likes

Topic		Replies	Views
Endless methods for Crystal Community	24	1189	December 10, 2023
RFC: `&.` within a block Crystal Contrib	61	3952	December 9, 2023
RFC: `with ... yield` replacement Crystal Contrib	57	4108	May 14, 2025
Verifying what an 'end' goes with Help & Support	4	495	December 10, 2019
My 2022 Crystal Wishlist Community	19	3048	March 11, 2022

Proposal: New "ends" keyword

Related topics