Skip to content

Commit 7bfdd2c

Browse files
committed
replace 'sigilled' with 'sigiled'
This PR is a very rough draft to fix #2660. Feedback welcome.
1 parent abbb9b5 commit 7bfdd2c

File tree

5 files changed

+14
-14
lines changed

5 files changed

+14
-14
lines changed

doc/Language/hashmap.pod6

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -71,7 +71,7 @@ able to use dates (or a part of them) as keys. Since we are parameterizing
7171
C<Associative> to those particular classes, C<of> will return the value type we
7272
have used, C<Cool> in this case (we can log lists or strings only). Mixing the C<Associative>
7373
role gives it the right to use the C<%> sigil; binding is needed in the definition since
74-
C<%>-sigilled variables get by default the C<Hash> type.
74+
C<%>-sigiled variables get by default the C<Hash> type.
7575
7676
This log is going to be append-only, that is why we escape the associative array
7777
metaphor to use a C<log> method to add new events to the log. Once they have
@@ -156,7 +156,7 @@ or
156156
my $h = { a => 'b', c => 'd', e => 'f'};
157157
158158
Please note that curly braces are used only in the case that we are not
159-
assigning it to a C<%>-sigilled variable; in case we use it for a C<%>-sigilled
159+
assigning it to a C<%>-sigiled variable; in case we use it for a C<%>-sigiled
160160
variable we will get an C<Potential difficulties:␤ Useless use of hash
161161
composer on right side of hash assignment; did you mean := instead?> error. As
162162
this error indicates, however, we can use curly braces as long as we use also
@@ -269,7 +269,7 @@ instead:
269269
Note: Rakudo implementation currently erroneously applies L<the same
270270
rules|/routine/{ }#(Operators)_term_{_}> for C<:{ }> as it does for C<{ }> and
271271
can construct a L<Block|/type/Block> in certain circumstances. To avoid that, you can
272-
instantiate a parameterized Hash directly. Parameterization of C<%>-sigilled
272+
instantiate a parameterized Hash directly. Parameterization of C<%>-sigiled
273273
variables is also supported:
274274
275275
my Num %foo1 = "0" => 0e0; # Str keys and Num values

doc/Language/terms.pod6

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -244,7 +244,7 @@ by default.
244244
245245
I<NOTE: if you're using the Rakudo compiler, you need version 2018.08 or
246246
newer for type constraints and auto-coercion on constants to be
247-
available. Auto-coercion on %-sigilled constants requires 6.d language,
247+
available. Auto-coercion on %-sigiled constants requires 6.d language,
248248
preview version of which can be enabled with the C«use v6.d.PREVIEW»
249249
pragma>
250250
@@ -260,11 +260,11 @@ our Int constant bar = 42;
260260
=end code
261261
262262
Unlike L<variables|/language/variables>, you cannot parameterize C<@>-,
263-
C<%>-, and C<&>-sigilled constants by specifying the parameterization
263+
C<%>-, and C<&>-sigiled constants by specifying the parameterization
264264
type in the declarator itself:
265265
266266
=begin code :skip-test<showcasing deliberate compile-time error>
267-
# !!WRONG!! cannot parameterize @-sigilled constant with Int
267+
# !!WRONG!! cannot parameterize @-sigiled constant with Int
268268
our Int constant @foo = 42;
269269
270270
# OK: parameterized types as values are fine
@@ -276,13 +276,13 @@ sigils default to L<List|/type/List> and L<Map|/type/Map> types, which cannot be
276276
parameterized. To keep things simple and consistent, parameterization
277277
was simply disallowed in these constructs.
278278
279-
The C<@>-, C<%>-, and C<&>-sigilled constants specify implied typecheck
279+
The C<@>-, C<%>-, and C<&>-sigiled constants specify implied typecheck
280280
of the given value for L<Positional|/type/Positional>, L<Associative|/type/Associative>, and L<Callable|/type/Callable>
281-
roles respectively. The C<@>-sigilled constants—and as of C<6.d>
282-
language version, the C<%>-sigilled constants as well—perform
281+
roles respectively. The C<@>-sigiled constants—and as of C<6.d>
282+
language version, the C<%>-sigiled constants as well—perform
283283
auto-coercion of the value if it does not pass the implied typecheck.
284-
The C<@>-sigilled constants will coerce using method L<cache|/routine/cache> and
285-
C<%>-sigilled constants coerce using method L<Map|/type/Map>.
284+
The C<@>-sigiled constants will coerce using method L<cache|/routine/cache> and
285+
C<%>-sigiled constants coerce using method L<Map|/type/Map>.
286286
287287
=begin code
288288
constant @foo = 42;

doc/Type/Any.pod6

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -392,7 +392,7 @@ Defined as:
392392
multi method hash(Any:D:)
393393
394394
When called on a type object, returns an empty L<Hash|/type/Hash>. On instances,
395-
it is equivalent to assigning the invocant to a C<%->sigilled variable and
395+
it is equivalent to assigning the invocant to a C<%->sigiled variable and
396396
returning that.
397397
398398
Subclasses of C<Any> may choose to return any I<core> type that does the

xt/word-variants.t

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,8 @@ my %variants = %( filehandle => 'file [\s+|\-] handle',
2424
NYI => 'niy',
2525
metaoperator => 'meta [\s+|\-] operator',
2626
semicolon => 'semi [\s+|\-] colon',
27-
metadata => 'meta [\s+|\+] data'
27+
metadata => 'meta [\s+|\+] data',
28+
sigiled => 'sigiled',
2829
);
2930
# zero-width in particular has several unicode documentation variants we allow
3031

xt/words.pws

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1170,7 +1170,6 @@ sigbus
11701170
sighup
11711171
sigil
11721172
sigiled
1173-
sigilled
11741173
sigilless
11751174
sigils
11761175
sigint

0 commit comments

Comments
 (0)