At least in unix creating files and folders are different operations (mkdir/touch, rm/rmdir).
And even though it may seem convenient I would argue that it will create unintentional issues ��� if you have incorrect folder it will silently create errornous structure on the disk instead of throwing error. Imho overloading ensureCreateFile is bad.
But there's nothing stopping you from extending AFR and adding an extra method:
AbstractFileReference>>ensureCreateFileAndDirectory
"Create if necessary a folder and file for the receiver."
self parent ensureCreateDirectory.
self ensureCreateFile
Peter