use case

Hi,

you ask for a proper use case for your wonderful alias function. I think it will be extremely useful to clarify code by allowing more readable assignment into deeply nested data structures that need to remain consistent. I frequently change e.g. the metadata of a deeply neseted object (e.g. sitting 3 or more levels deep in the main object). All too often I create a temporary copy of the relevant bits for brevity, then modify that but forget to reassign it back into the main state properly. It may be syntactic sugar but if it helps clarify code I think it's very valuable to have (cf. all the tidyverse stuff, that is also syntactic sugar to a large degree).

Is it safe to assume that `aka::alias` will work in all R versions simply because it is syntactic sugar for `makeActiveBinding`, which has been/will always be present in R ?

Start by reading the `aka::alias` entry point and R's `makeActiveBinding` documentation, then check the package's supported R versions. The issue does not name a file, test, concrete change, or acceptance criteria; clarify whether it requests documentation, compatibility guarantees, or an implementation change before starting.

Written by the indexing model from the issue text.