What is the desired addition or change?

Right now we don't have implementation of copy and move constructors in layer which is causing memory issues.

What is the motivation for this feature?

Follow #2314 to see the memory issues we were facing.

If applicable, de

I'm sorry if I missed this functionality, but CLI version hasn't it for sure (I saw the related code only in generate_code_examples.py). I guess it will be very useful to eliminate copy-paste phase, especially for large models.

Of course, piping is a solution, but not for development in Jupyter Notebook, for example.

Description

It would be nice if there is a copy button in the docs and readme examples to make it easier for users to try the examples and play with the code. This should be easy to implement, maybe using a sphinx library. The docs are in the docs folder in the repo, I will let this issue open for new comers ;)

Unlike N-Gram, the current Skip-Gram tokenizer does not allow variable length tokens. This ticket is to implement a min max scheme similar to the N-Gram tokenizer such that each token is a k-skip-n-gram. In other words, instead of fi