Challenge 1: Build and Access an Array — Possible Solution
====================================================================

use strict;
use warnings;
use feature 'say';

my @foods = ("pizza", "sushi", "tacos", "pasta");

say $foods[0];     # first element
say $foods[-1];    # last element
say scalar(@foods);

Output:
pizza
pasta
4

WHY THIS WORKS AS AN ANSWER
------------------------------
my @foods = (...) reuses the chapter's own array-declaration pattern
exactly, with 4 string elements per the challenge's requirement.

$foods[0] reuses the chapter's own $ vs @ sigil-switch rule directly
— even though the array itself is @foods, asking for ONE specific
element (the first one, at index 0) uses $, per the warn-box's own
explanation that the sigil describes what's being asked for, not the
variable's underlying identity.

$foods[-1] reuses the chapter's own negative-indexing example exactly
— -1 counts from the end, so it retrieves the last element ("pasta")
without needing to know or calculate how many elements the array
actually has.

scalar(@foods) reuses the chapter's own scalar() call, forcing @foods
into scalar context explicitly — per the chapter's List vs. Scalar
Context section, this returns the element COUNT (4), the same
underlying context-sensitivity demonstrated there with my $count =
@fruits;, just made explicit here with the scalar() function instead
of relying on an assignment's own implicit context.