Tim

On Amazon EC2: ``` # Amazon AMI Linux yum install autoconf automake libtool nasm ``` VERY not happy I have to install all this crap on my build server to...

Well let's see what happens here... ``` yum install autoconf automake libtool nasm ``` This is all done so that `cjpeg` can be built, which seems to be a part...

The point is, rather than having to pick and pull from different statically-linked libraries that _may or may not_ exist in varying distros of linux, it's better to pull all...

the problem is.. what does the usage syntax look like? ```node await (user.password = 'some-secure-password'); ``` This doesn't work. According to [ECMA262 12.15.4](https://tc39.github.io/ecma262/#sec-assignment-operators-runtime-semantics-evaluation), the return value of `user.password = 'some-secure-password'`...

You could also just do this: ```node User.methods.setPassword = async function (password) { const hashedPassword = await hashPassword(password); this.password = hashedPassword; await this.save(); return this; }; ``` ```node const myUser...

@gcanu you're completely ignoring what I posted, what you are proposing returns a Promise from an assignment call and that completely breaks the Javascript/ECMA262 specification. For your code snippet to...

@vkarpov15 This is not a mongoose-specific issue but rather questioning the validity of the current ECMAScript spec. This "feature request" should be closed...

@fundon , Tell me this: How exactly will you call your virtual setter? Please show the usage. If you're using `async` it must be handled by a promise. Your original...

My example code is just an example... you can also do this so easily: ```node User.methods.setPassword = async function (password) { const hashedPassword = await hashPassword(password); this.password = hashedPassword; return...

why? so you can save a few lines of code? the reason isn't enough to justify all the extra work and possibly breaking changes to the codebase.