-
Notifications
You must be signed in to change notification settings - Fork 0
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
Align Go structs #73
Open
igo95862
wants to merge
1
commit into
master
Choose a base branch
from
align-go-structs
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Align Go structs #73
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
TDPROTO: auth.go:3:11: struct with 544 pointer bytes could be 520 billing_change_tariff.go:6:26: struct with 88 pointer bytes could be 80 billing_change_tariff.go:19:49: struct with 40 pointer bytes could be 32 billing_personal_account.go:6:29: struct of size 184 could be 176 billing_tariff.go:6:20: struct with 144 pointer bytes could be 104 billing_tariff.go:69:26: struct of size 128 could be 120 billing_tariff.go:126:26: struct with 40 pointer bytes could be 32 billing_team.go:6:18: struct with 40 pointer bytes could be 32 billing_workplace.go:15:15: struct with 72 pointer bytes could be 64 billing_workplace.go:112:61: struct with 32 pointer bytes could be 24 call_event.go:4:16: struct of size 136 could be 128 call_event.go:37:18: struct with 80 pointer bytes could be 72 call_event.go:61:17: struct with 16 pointer bytes could be 8 chat.go:34:11: struct of size 904 could be 856 chat.go:247:14: struct with 88 pointer bytes could be 72 chat.go:271:15: struct with 64 pointer bytes could be 32 client_call_offer.go:12:28: struct of size 64 could be 56 client_call_screenshare.go:12:34: struct with 16 pointer bytes could be 8 client_chat_composing.go:12:26: struct with 64 pointer bytes could be 56 client_chat_composing.go:20:32: struct with 32 pointer bytes could be 16 client_chat_lastread.go:12:25: struct with 56 pointer bytes could be 48 client_chat_lastread.go:20:31: struct with 24 pointer bytes could be 16 client_message_updated.go:19:33: struct of size 504 could be 496 color_rule.go:4:16: struct with 152 pointer bytes could be 120 contact.go:4:14: struct of size 688 could be 656 counters.go:4:19: struct with 72 pointer bytes could be 48 counters.go:29:18: struct with 24 pointer bytes could be 16 dlp.go:6:19: struct with 48 pointer bytes could be 40 dlp.go:41:15: struct with 600 pointer bytes could be 592 event.go:10:15: struct with 40 pointer bytes could be 32 features.go:9:15: struct of size 1544 could be 1472 icon_data.go:16:15: struct with 120 pointer bytes could be 104 integrations.go:4:23: struct with 32 pointer bytes could be 24 integrations.go:28:18: struct with 136 pointer bytes could be 128 markup_entity.go:8:19: struct with 104 pointer bytes could be 72 message.go:25:21: struct of size 376 could be 368 message.go:109:14: struct of size 768 could be 736 message.go:214:18: struct with 96 pointer bytes could be 80 message.go:240:22: struct with 32 pointer bytes could be 24 section.go:4:14: struct with 56 pointer bytes could be 40 server_call_answer.go:22:29: struct with 104 pointer bytes could be 96 server_call_buzz.go:31:27: struct with 728 pointer bytes could be 712 server_call_screenshare.go:20:34: struct with 32 pointer bytes could be 24 server_chat_composing.go:21:32: struct with 48 pointer bytes could be 40 server_chat_deleted.go:23:30: struct with 32 pointer bytes could be 16 server_chat_lastread.go:20:31: struct with 32 pointer bytes could be 16 server_chat_updated.go:24:30: struct with 32 pointer bytes could be 16 server_message_received.go:4:22: struct with 56 pointer bytes could be 40 server_message_updated.go:26:27: struct with 104 pointer bytes could be 96 server_message_updated.go:34:33: struct with 72 pointer bytes could be 48 server_online.go:43:17: struct with 64 pointer bytes could be 56 server_uisettings.go:13:23: struct with 56 pointer bytes could be 48 server_uisettings.go:18:29: struct with 24 pointer bytes could be 16 server_warning.go:11:20: struct with 64 pointer bytes could be 56 server_warning.go:19:26: struct with 32 pointer bytes could be 24 session.go:4:14: struct with 96 pointer bytes could be 88 short_message.go:4:19: struct with 96 pointer bytes could be 88 stats.go:8:26: struct with 88 pointer bytes could be 80 stickerpack.go:14:14: struct with 456 pointer bytes could be 448 task_preview.go:8:18: struct with 112 pointer bytes could be 104 task_status.go:4:17: struct with 48 pointer bytes could be 40 task_tabs.go:44:14: struct with 96 pointer bytes could be 88 team.go:4:11: struct of size 1152 could be 1120 upload.go:4:13: struct of size 160 could be 152 user.go:4:11: struct with 256 pointer bytes could be 248 user_auth.go:13:15: struct with 160 pointer bytes could be 144 TDAPI: atlinks.go:15:13: struct with 64 pointer bytes could be 56 auth.go:13:11: struct with 536 pointer bytes could be 504 auth.go:21:30: struct with 16 pointer bytes could be 8 auth.go:26:26: struct with 48 pointer bytes could be 40 auth.go:33:36: struct with 48 pointer bytes could be 40 chats.go:3:17: struct with 224 pointer bytes could be 200 color_rule.go:4:16: struct of size 104 could be 80 contact.go:11:14: struct of size 304 could be 280 draft.go:6:12: struct with 56 pointer bytes could be 48 group.go:12:12: struct with 96 pointer bytes could be 80 hotmessages.go:6:18: struct with 888 pointer bytes could be 784 integration.go:5:18: struct with 80 pointer bytes could be 64 message.go:5:20: struct with 328 pointer bytes could be 312 message.go:64:20: struct with 16 pointer bytes could be 8 message.go:75:14: struct with 96 pointer bytes could be 80 resp.go:6:11: struct with 88 pointer bytes could be 80 sharplinks.go:30:20: struct of size 72 could be 64 task.go:6:11: struct with 248 pointer bytes could be 240 task.go:60:17: struct with 344 pointer bytes could be 328 team.go:5:11: struct with 72 pointer bytes could be 56 upload.go:5:19: struct with 88 pointer bytes could be 72
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
TDPROTO:
auth.go:3:11: struct with 544 pointer bytes could be 520
billing_change_tariff.go:6:26: struct with 88 pointer bytes could be 80
billing_change_tariff.go:19:49: struct with 40 pointer bytes could be 32
billing_personal_account.go:6:29: struct of size 184 could be 176
billing_tariff.go:6:20: struct with 144 pointer bytes could be 104
billing_tariff.go:69:26: struct of size 128 could be 120
billing_tariff.go:126:26: struct with 40 pointer bytes could be 32
billing_team.go:6:18: struct with 40 pointer bytes could be 32
billing_workplace.go:15:15: struct with 72 pointer bytes could be 64
billing_workplace.go:112:61: struct with 32 pointer bytes could be 24
call_event.go:4:16: struct of size 136 could be 128
call_event.go:37:18: struct with 80 pointer bytes could be 72
call_event.go:61:17: struct with 16 pointer bytes could be 8
chat.go:34:11: struct of size 904 could be 856
chat.go:247:14: struct with 88 pointer bytes could be 72
chat.go:271:15: struct with 64 pointer bytes could be 32
client_call_offer.go:12:28: struct of size 64 could be 56
client_call_screenshare.go:12:34: struct with 16 pointer bytes could be 8
client_chat_composing.go:12:26: struct with 64 pointer bytes could be 56
client_chat_composing.go:20:32: struct with 32 pointer bytes could be 16
client_chat_lastread.go:12:25: struct with 56 pointer bytes could be 48
client_chat_lastread.go:20:31: struct with 24 pointer bytes could be 16
client_message_updated.go:19:33: struct of size 504 could be 496
color_rule.go:4:16: struct with 152 pointer bytes could be 120
contact.go:4:14: struct of size 688 could be 656
counters.go:4:19: struct with 72 pointer bytes could be 48
counters.go:29:18: struct with 24 pointer bytes could be 16
dlp.go:6:19: struct with 48 pointer bytes could be 40
dlp.go:41:15: struct with 600 pointer bytes could be 592
event.go:10:15: struct with 40 pointer bytes could be 32
features.go:9:15: struct of size 1544 could be 1472
icon_data.go:16:15: struct with 120 pointer bytes could be 104
integrations.go:4:23: struct with 32 pointer bytes could be 24
integrations.go:28:18: struct with 136 pointer bytes could be 128
markup_entity.go:8:19: struct with 104 pointer bytes could be 72
message.go:25:21: struct of size 376 could be 368
message.go:109:14: struct of size 768 could be 736
message.go:214:18: struct with 96 pointer bytes could be 80
message.go:240:22: struct with 32 pointer bytes could be 24
section.go:4:14: struct with 56 pointer bytes could be 40
server_call_answer.go:22:29: struct with 104 pointer bytes could be 96
server_call_buzz.go:31:27: struct with 728 pointer bytes could be 712
server_call_screenshare.go:20:34: struct with 32 pointer bytes could be 24
server_chat_composing.go:21:32: struct with 48 pointer bytes could be 40
server_chat_deleted.go:23:30: struct with 32 pointer bytes could be 16
server_chat_lastread.go:20:31: struct with 32 pointer bytes could be 16
server_chat_updated.go:24:30: struct with 32 pointer bytes could be 16
server_message_received.go:4:22: struct with 56 pointer bytes could be 40
server_message_updated.go:26:27: struct with 104 pointer bytes could be 96
server_message_updated.go:34:33: struct with 72 pointer bytes could be 48
server_online.go:43:17: struct with 64 pointer bytes could be 56
server_uisettings.go:13:23: struct with 56 pointer bytes could be 48
server_uisettings.go:18:29: struct with 24 pointer bytes could be 16
server_warning.go:11:20: struct with 64 pointer bytes could be 56
server_warning.go:19:26: struct with 32 pointer bytes could be 24
session.go:4:14: struct with 96 pointer bytes could be 88
short_message.go:4:19: struct with 96 pointer bytes could be 88
stats.go:8:26: struct with 88 pointer bytes could be 80
stickerpack.go:14:14: struct with 456 pointer bytes could be 448
task_preview.go:8:18: struct with 112 pointer bytes could be 104
task_status.go:4:17: struct with 48 pointer bytes could be 40
task_tabs.go:44:14: struct with 96 pointer bytes could be 88
team.go:4:11: struct of size 1152 could be 1120
upload.go:4:13: struct of size 160 could be 152
user.go:4:11: struct with 256 pointer bytes could be 248
user_auth.go:13:15: struct with 160 pointer bytes could be 144
TDAPI:
atlinks.go:15:13: struct with 64 pointer bytes could be 56
auth.go:13:11: struct with 536 pointer bytes could be 504
auth.go:21:30: struct with 16 pointer bytes could be 8
auth.go:26:26: struct with 48 pointer bytes could be 40
auth.go:33:36: struct with 48 pointer bytes could be 40
chats.go:3:17: struct with 224 pointer bytes could be 200
color_rule.go:4:16: struct of size 104 could be 80
contact.go:11:14: struct of size 304 could be 280
draft.go:6:12: struct with 56 pointer bytes could be 48
group.go:12:12: struct with 96 pointer bytes could be 80
hotmessages.go:6:18: struct with 888 pointer bytes could be 784
integration.go:5:18: struct with 80 pointer bytes could be 64
message.go:5:20: struct with 328 pointer bytes could be 312
message.go:64:20: struct with 16 pointer bytes could be 8
message.go:75:14: struct with 96 pointer bytes could be 80
resp.go:6:11: struct with 88 pointer bytes could be 80
sharplinks.go:30:20: struct of size 72 could be 64
task.go:6:11: struct with 248 pointer bytes could be 240
task.go:60:17: struct with 344 pointer bytes could be 328
team.go:5:11: struct with 72 pointer bytes could be 56
upload.go:5:19: struct with 88 pointer bytes could be 72