Question: <https://colab.research.google.com/notebooks/io.ipynb#scrollTo=KHeruhacFpSU>

In this notebook help it explains how to upload a file to drive and then download to Colaboratory but my files are already in drive.

Where can I find the file ID ?

```
# Download the file we just uploaded.
#
# Replace the assignment below with your file ID
# to download a different file.
#
# A file ID looks like: 1uBtlaggVyWshwcyP6kEI-y_W3P8D26sz
file_id = 'target_file_id'

```

Answer: 
If the parameter is definitely unused, `[[maybe_unused]]` is not particularly useful, unnamed parameters and comments work just fine for that.

`[[maybe_unused]]` is mostly useful for things that are *potentially* unused, like in

```
void fun(int i, int j) {
    assert(i < j);
    // j not used here anymore
}

```

This can't be handled with unnamed parameters, but if `NDEBUG` is defined, will produce a warning because `j` is unused.

Similar situations can occur when a parameter is only used for (potentially disabled) logging.
I find [[maybe\_unused]] is useful when you have a set of constants that define a set configuration constants that may or may not be used depending on the configuration. You are then free to change the configuration without having to define new constants and worrying about unused constants.

I use this mainly in embedded code where you have to set specific values. Otherwise enumerations are generally better.