January 2024 - ruby-core - ml.ruby-lang.org

[ruby-core:115993] [Ruby master Feature#16495] Inconsistent quotes in error messages

by ivoanjo (Ivo Anjo)

Issue #16495 has been updated by ivoanjo (Ivo Anjo). matz (Yukihiro Matsumoto) wrote in #note-7: > It was something cultural. I admit nowadays very few people use backquote as a left-hand quote, but it used to be. I also admit consistent quotes are easier for our eyes when using recent major fonts. But changing those quotes may affect existing log parsers. We have to estimate how big is the influence of the changes. > > Matz. On the topic of impacting the ecosystem, there have been quite a few changes to how exceptions have been displayed recently: * https://bugs.ruby-lang.org/issues/17930 * https://bugs.ruby-lang.org/issues/18564 and even more being discussed https://bugs.ruby-lang.org/issues/19117 . Overall the impact on the ecosystem seemed quite small, and the gain in usability was nice. So changing the `` ` `` to a `'` doesn't seem like it would be worse than any of those changes. ---------------------------------------- Feature #16495: Inconsistent quotes in error messages https://bugs.ruby-lang.org/issues/16495#change-105958 * Author: Kolano (Kenneth Kolano) * Status: Open * Priority: Normal * Assignee: matz (Yukihiro Matsumoto) ---------------------------------------- Error messages use inconsistent pairs of quotes, for instance: ``` -e:1:in `<main>': undefined local variable or method `foo' for main:Object (NameError) ``` where a back tick is used on the left-hand side, and a single quote is used on the right. The same quotes should be used on either side of the elements being quoted. -- https://bugs.ruby-lang.org/

4 months, 1 week

1
0
0 0

[ruby-core:115988] [Ruby master Bug#20110] Issue 193

by jay232857 (jay singh)

Issue #20110 has been reported by jay232857 (jay singh). ---------------------------------------- Bug #20110: Issue 193 https://bugs.ruby-lang.org/issues/20110 * Author: jay232857 (jay singh) * Status: Open * Priority: Normal * Backport: 3.0: UNKNOWN, 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN ---------------------------------------- Tiger Shipping Containers has been Australia’s leading container company for over 30 years. We sell containers, hire containers, and modify containers, both new and 2nd hand, in 40ft, 20ft and 10ft sizes. With container delivery available (often within 24 hours) right across Australia. When you purchase a container from Tiger Shipping Containers, you do so safe in the knowledge that you’re buying from the largest container wholesaler in Australia. And as the country’s preeminent container wholesaler, we are in the very fortunate position of being able to get container stock into our various depots around the country in quantities that that nobody else can. And because we buy containers in bulk, it allows us to heavily discount our stock when we sell direct to the public. [[https://www.tigershippingcontainers.com.au/]] Tiger Shipping Containers has the container stock you need in stock right now. We have the (local) depots around the country to allow us to deliver your container quickly (often with 24 hours!). And as Australia’s largest container wholesaler we can discount our containers and sell them at a price that is impossible for our competition to match. So whether you’re buying a new or used container, or simply hiring a container for a set period of time, Tiger Shipping Containers is the only call you’ll ever have to make. -- https://bugs.ruby-lang.org/

4 months, 1 week

1
1
0 0

[ruby-core:115987] [Ruby master Bug#20109] Issue 101

by nina569 (nina cooper)

Issue #20109 has been reported by nina569 (nina cooper). ---------------------------------------- Bug #20109: Issue 101 https://bugs.ruby-lang.org/issues/20109 * Author: nina569 (nina cooper) * Status: Open * Priority: Normal * Backport: 3.0: UNKNOWN, 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN ---------------------------------------- Manually keeping track of unique IDs is almost next to impossible but something like this example has the potential to categorize per functionality and testing stage and will expand and contract the list (to an extent.) On the lookout for a tiles shop in Sydney for your hotel [[reception]] project? Unsure about which tiles to use for your new house? Searching for the right tiles that would fit the color scheme of your bathroom renovation at home? https://tilearte.com.au/ -- https://bugs.ruby-lang.org/

4 months, 1 week

1
0
0 0

[ruby-core:115981] [Ruby master Bug#20105] Introduce `IO::Stream` or something similar.

by ioquatix (Samuel Williams)

Issue #20105 has been reported by ioquatix (Samuel Williams). ---------------------------------------- Bug #20105: Introduce `IO::Stream` or something similar. https://bugs.ruby-lang.org/issues/20105 * Author: ioquatix (Samuel Williams) * Status: Open * Priority: Normal * Assignee: ioquatix (Samuel Williams) * Backport: 3.0: UNKNOWN, 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN ---------------------------------------- Ruby's IO class has a general model for streaming IO, including some hidden classes like `IO::generic_readable` and `IO::generic_writable`. As Ruby's core IO classes evolve, gems like `openssl` (see `OpenSSL::Buffering`) need to be updated to support changes to the interface. As it stands, there are changes in `IO` which are not copied to `OpenSSL::Buffering`. I'd like to propose we introduce some shared interface for streams that is used by `IO`, `Socket`, and `OpenSSL` to start with. The general interface would be similar to `IO` and allow code like `OpenSSL` to avoid re-implementing the `IO` interface. -- https://bugs.ruby-lang.org/

4 months, 1 week

1
0
0 0

2024

2023

2022

ruby-core January 2024