This is a soft-question about an aspect of Julia’s design and history. It’s a well-discussed point that scalars are iterable, in the sense that: julia> 42[1], 42[], size(42), length(42) (42, 42, (), 1) julia> collect(42) 0-dimensional Array{Int64,0}: 42 I previously thought that a primary reason…

Simple answer: Broadcast.broadcastable was implemented quite recently as compared to the iterable-ness of scalars — I believe it was even more recently than their most recent excision attempt.

Why are scalars iterable when broadcasting would still work fine if they weren't?

Internals & Design

stevengj July 26, 2022, 3:24am 3

See Map vs list comprehension - #9 by stevengj

Topic		Replies	Views
recent broadcast changes (iterate by default), scalar struct, and `@.` Internals & Design broadcast	68	8156	January 9, 2019
Broadcasting structs as scalars General Usage question	5	2585	August 30, 2018
A more intuitive way to treat an object as a scalar in broadcasting? Internals & Design broadcast	9	753	March 5, 2020
X .-= 2 for scalar x fails General Usage question	1	709	October 11, 2018
Should scalar calculation in Broadcast be "lazy"? Internals & Design broadcast	12	1007	August 10, 2020

Why are scalars iterable when broadcasting would still work fine if they weren't?

Related topics