For each fixed , , so the only possible limit is zero. But taking gives for every . In fact the supremum of over the interval is infinite for each . Thus the convergence is pointwise but not uniform; uniform convergence cannot be inferred from convergence at each fixed point.
Change the generators to , and . This is an invertible integer change of generators, since , , . The relations become and , with no relation involving . Consequently
This is already the invariant-factor order required by the structure theorem for finitely generated modules over a principal ideal domain, because . The inverse change of generators shows that there are no hidden extra relations.
The structure theorem for finitely generated modules over a principal ideal domain applies because every Euclidean domain is a principal ideal domain. In invariant-factor form, every finitely generated module over such a domain has a decomposition
where the are nonzero nonunits, , and either list of summands may be empty. The free rank and the invariant factors are unique up to multiplication of each by a unit. Equivalently the torsion part is a direct sum of cyclic modules with prime-power annihilators. The nonunit convention omits zero summands .
A Euclidean domain is a commutative integral domain with a function such that, for with , there are satisfying , where either or . One may also impose the usual monotonicity for nonzero ; the example below has it.
The integers form a Euclidean domain that is not a field. Use . Integer division by supplies a remainder with , and changing the sign of the quotient handles negative . The integers are an integral domain, while has no multiplicative inverse in them. This verifies both the Euclidean property and the failure to be a field.
One excursion from zero escapes forever on the positive branch with probability , and on the negative branch with probability . The remaining probability is the return probability . By the last-excursion direction law at a transient junction, the eventual positive escape probability is
Equivalently, if denotes the desired probability, the Strong Markov property gives . The negative escape probability is , and their sum is one, as independently established in part (b).
On the negative branch set . Its outward step probability is and inward probability is . The same finite gambler's ruin recurrence as in part (a), with root , gives . Hence, following one departure from zero, the probability of returning is
At each return the Strong Markov property restarts the same excursion experiment. The probability of at least returns is , tending to zero. Thus almost surely there is a last visit to zero.
After that visit the walk remains strictly positive or strictly negative, because nearest-neighbour steps cannot change sign without crossing zero. On the positive branch it can be coupled, up to any return, to independent steps of mean . The strong law of large numbers gives a walk tending to almost surely. This conclusion remains true on the event that the excursion never returns: conditioning on a positive-probability event cannot make a probability-zero failure of the law occur. On the negative branch the mean step is , giving in the same way. Apply this at each possible departure time, a countable family, or use the Strong Markov property at the successive returns. Therefore
Finite visits to zero alone would not prove divergence on an arbitrary chain; the outward-drift argument is the additional step needed here.
Until the first visit to zero, the positive-side chain is a nearest-neighbour random walk with upward probability and downward probability . For an integer , let , . The Markov property gives
The characteristic roots of this recurrence are and . Solving its two boundary equations gives the biased gambler's ruin probability
A finite path that reaches zero has a finite maximum before doing so, and is counted by for every sufficiently large . Conversely each such event implies a visit to zero. Therefore these events increase to , and continuity of probability gives
More generally the hitting probability from is . The finite-boundary derivation avoids choosing an unjustified solution of the infinite recurrence.
Write , finite and positive. Exactness on the constant polynomial gives . Positivity therefore implies the uniform operator bound , and the integral has the same bound.
For a continuous and , the Weierstrass approximation theorem gives a fixed polynomial of degree with . For every , polynomial exactness gives . Thus
Since is arbitrary, for every continuous . This is convergence of positive quadrature on continuous functions. The argument requires nodes in , implicit in a rule defined on all continuous functions there; otherwise their function values would not even be specified by the stated domain. Exactness alone would not provide the norm bound if arbitrarily signed weights were allowed.
For node , let be the Lagrange interpolation polynomial with . It has degree , so has degree . The Gaussian quadrature with nodes is exact through degree , hence
The integrand is nonnegative. Since is a nonzero polynomial, it is nonzero on some open subinterval; the positive weight has positive integral there. Consequently for every node. This proves the positive weights of Gaussian quadrature property without assuming any coefficient sign beforehand.
Relabel the two primes so that . By the Sylow theorems, the number of Sylow -subgroups divides , so it is either or . But and , ruling out . Thus there is a unique Sylow subgroup of order , which is a normal subgroup. It is nontrivial and proper because . Consequently no group of order is simple. No additional assumption on divisibility of by is required.
The remaining Sylow theorems state that every -subgroup of a finite group is contained in a Sylow subgroup, and that all Sylow -subgroups are conjugate. If with and is the number of Sylow -subgroups, then
In particular if and only if that Sylow subgroup is a normal subgroup.
Let be the set of all subsets of with elements. First show that is not divisible by . In the polynomial ring over the field of elements, , since the intermediate binomial coefficients are divisible by . Iterating gives
Comparison of coefficients of yields .
Let act on by left translation. Because its orbit sizes sum to a number not divisible by , some orbit has size prime to . Choose a subset in that orbit, with stabilizer . The orbit-stabilizer theorem gives the orbit size , so . On the other hand acts freely on the elements of : if , cancellation in the group gives . Every -orbit in therefore has elements, and divides . Since
and the second factor has no factor of , the first must contain all . Hence , proving the first of the Sylow theorems. This is Sylow existence by subset action and includes the trivial case .
At the first step of Gaussian elimination, the first column of a nonsingular matrix cannot be zero. Choose a nonzero pivot there using a row interchange and eliminate below it. The resulting matrix has block form
Elementary elimination and row permutations preserve nonsingularity, so and the trailing matrix is nonsingular. Its first column again has a nonzero entry. Repeating this argument inductively provides a nonzero pivot at every step and produces an upper-triangular factor. The recorded elimination multipliers, with previous entries permuted when necessary, form the unit lower-triangular factor. Every nonsingular square matrix admits under columnwise partial pivoting.
For the column-interchange convention from part (a), use the same induction with a nonzero entry in the first row of each nonsingular trailing matrix. Column interchanges put it in the pivot position, and elimination gives . These existence statements are in exact arithmetic; they do not assert that all choices have equally good numerical stability.
Use columnwise partial pivoting: select the largest absolute entry in the current column and interchange rows. In the first column the pivot is , so interchange rows 1 and 2. The multipliers are and , and elimination gives
The second pivot is , so interchange the two remaining rows. Their previously stored first-column multipliers must also be interchanged. The final multiplier is , giving the LU decomposition
The permutation matrix orders the original rows as . Multiplication verifies the displayed identity.
If “column pivoting” instead denotes interchanging columns rather than searching within a column, that convention gives with
This second identity uses a different pivot convention; it does not change the row-pivoted answer above.
Parametrize the logarithmic spiral by
The map is continuous into the ambient plane, hence into with its subspace topology, and it is onto by the definition of the spiral. It is injective because its radius determines uniquely, even when the angular coordinate winds through repeated turns.
Every point of is nonzero. The inverse is therefore
the restriction of a continuous function on the punctured plane. Hence is a homeomorphism and the spiral is homeomorphic to the real line. Its accumulation at the origin causes no failure of this argument: the origin is not included in .
The product topology on consists of arbitrary unions of rectangles , with open in and open in . Equivalently, these rectangles form a basis.
The empty set is the empty union, and is itself an allowed rectangle. An arbitrary union of sets of this form is still a union of allowed rectangles. Finally,
which is an allowed rectangle because the factor topologies are closed under finite intersections. Distributing intersection over unions shows that the intersection of any two product-open sets is product-open; induction handles all finite intersections. These verify every topology axiom. Rectangles alone are generally not a topology, which is why their arbitrary unions are included.
A collections library can specify a List<E> Java interface, with different implementations such as ArrayList<E> and LinkedList<E>. A method accepting List<E> can iterate or access elements according to the documented list contract without requiring one particular storage representation. Each implementation may also extend its own appropriate class superclass.
The benefit is separating a usable contract from its implementation. A parameter restricted to a concrete ArrayList<E> would exclude a linked list implementation and unnecessarily expose the storage choice. Requiring all providers to extend one concrete class would couple them to its implementation and consume Java's single class-inheritance relationship. Interfaces permit multiple implemented contracts, though clients must rely on the stated contract rather than assuming every optional operation is supported or has the same time complexity.
A growable-array library should store its backing Java array and logical size in private fields in Java. Public methods such as add, get and remove can enforce bounds and keep the size consistent with the stored elements. The representation can later change without requiring clients to modify direct field accesses.
The benefit is preserving invariants through encapsulation. If clients could assign the size or replace the backing Java array directly, they could create negative sizes, report elements that do not exist, or modify entries without the library's checks. Accessor methods should not expose a mutable backing object indiscriminately, since a private field alone does not prevent that indirect route. Private fields also do not provide a general security boundary against privileged reflection or native code; the point here is ordinary library access discipline.
A collections library can supply a genuinely generic method in Java whose own type parameter connects the input element and the result element type:
java
static <T> java.util.List<T> oneElement(T item) {
    java.util.List<T> result = new java.util.ArrayList<T>();
    result.add(item);
    return result;
}
For example, List<String> xs = oneElement("sample"); is type-checked without a cast. The method can also construct a List<Integer> from an integer object. The standard library's Collections.singletonList is another example of this type relationship, though its returned list is unmodifiable.
The benefit is one reusable implementation with compile-time argument/result consistency. A raw List result would lose element-type information, invite unchecked calls and require casts that may fail later. Separate methods for every element type would duplicate code. Merely enclosing a concrete type in angle brackets, such as returning List<String>, does not make a method generic; the method here declares <T>. Type erasure means the guarantee is primarily a source-level type check, not a distinct runtime class for each type argument.
An immutable library value such as java.lang.String can be a final class in Java. No class can extend it, so a client receiving a String cannot secretly receive a subclass that changes the behavior of its methods. This protects assumptions about value semantics in code using strings as keys or trusted identifiers.
The benefit is a closed implementation contract. Without final, subclasses might override methods inconsistently or introduce behavior incompatible with the library's intended guarantees. Making a class final does not by itself make its fields immutable; a correct immutable implementation also controls its state. The cost is that clients cannot customize it by inheritance and must instead use composition or a different abstraction.

There are unlisted articles, also show them or only show them.