Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Why the oldChild param of HtmlNode.ReplaceChild not at the front? #417

Open
GF-Huang opened this issue Nov 30, 2020 · 1 comment
Open

Why the oldChild param of HtmlNode.ReplaceChild not at the front? #417

GF-Huang opened this issue Nov 30, 2020 · 1 comment
Assignees

Comments

@GF-Huang
Copy link

image

It's anti human. It's against habits.

Look at the string.Replace, it's old at front.

image

@JonathanMagnan JonathanMagnan self-assigned this Nov 30, 2020
@JonathanMagnan
Copy link
Member

Hello @GF-Huang ,

I agree.

However, that's impossible to change the order due to backward compatibility. All we will do is introducing a lot of bugs so the only option left is creating a new method and I'm not really sure that this solution is really better.

Best Regards,

Jon


Performance Libraries
context.BulkInsert(list, options => options.BatchSize = 1000);
Entity Framework ExtensionsEntity Framework ClassicBulk OperationsDapper Plus

Runtime Evaluation
Eval.Execute("x + y", new {x = 1, y = 2}); // return 3
C# Eval FunctionSQL Eval Function

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants