Docker Compose v3

Docker compose v3 is out and with it are gone all the constraint options (cpu_shares, cpu_quota, cpuset, mem_limit, memswap_limit), which have been moved to the new “deploy” section, for better integration with Docker Swarm (see here).
Since the scheduler takes into account both memoryReservation and milliCpuReservation fields for deciding container allocation in the hosts, should I worry about these old (but still current) docker compose options not being supported by Rancher in future versions?

Reservations are Rancher options for making scheduling decisions and unrelated to the runtime options in the docker engine for limiting the resources the container can actually take.